Option not to hydrate the Portal Item

Open
#2,294 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start with the ArcGIS API for Python's PortalItem handling and reproduce the reported management-script operations on a machine that cannot reach the external services. Define how an opt-out from automatic hydration should affect item operations, and verify that layer data is loaded only when explicitly requested while existing PortalItem behavior remains available.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem? Please describe.
I've registered some external public services in my Portal, my end users can access these services on their systems in the browser and in ArcGIS Pro.
I also have a machine where I run some management scripts and this machine cannot communicate with internet resources and these external services, but it can communicate with my Portal.
When I run my scripts with ArcGIS API for Python it loads these Portal Items and try do do things, such as setting the delete protection property, sharing the item etc, and it takes a lot of time, like multiple minutes for each operation.
I think this is because everything I try to do is forcing ArcGIS API for Python to rehydrate the PortalItem and in this process, it tries to reload the layers from the external service, which cannot be accessed from the machine and this script.

<insert your code here>

Describe the solution you'd like
Have the option to only rehydrate on demand, by setting some kind of boolean which prevents the current automatic rehydrates, or maybe have the option not to load the layers in some way?

Describe alternatives you've considered
Do to the security policies, allowlisting on the firewall / proxy isn't possible on this machine, otherwise I would have done that.

Additional context

Thanks for considering :-)

Dominant language
Python
Stars
2.2k
Forks
1.1k
Avg merge
2h 40m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Esri/arcgis-python-api

All issues in Esri/arcgis-python-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.