Add a trusted toolbox list or a don't ask again button for 3rd party code warning when refreshing a Toolbox.

[GISDepartmentMFM]

A new feture was recently added to ArcGIS Pro so that when a python toolbox is refreshed it will popup with the Warning: "

Opening a Python toolbox runs third-party code. Confirm you trust the source before proceeding.

(file Path)

Allow this toolbox code to run?

"

This warning gets really annoying when developing python toolboxes and it would be nice if there was a way to permanently mark it as a trusted 3rd party for the project with a "do not ask again" button or be able to set a trusted directory that has all the users toolboxes as white listed and  to not show the warning again.

[DrewFlater]

We are treating the Security warning on Refresh as a defect at this time, to be addressed in the near term. 

If you only use Python Toolboxes from yourself/your organization which are all trusted, you could consider setting BlockNonSystemPythonToolbox to No.

https://pro.arcgis.com/en/pro-app/latest/get-started/geoprocessing-settings.htm#ESRI_SECTION1_88A083... 

[philnagel]

Any more info on this? I reached out to support to get the defect attached to our org and was told it was not in the system. 

[HannesZiegler]

Hey @philnagel, sorry for the confusion, since this came in by a different route (identified by way of your ideas post), there's no support ticket for it. I confirmed there is an internal issue tracking this bug for inclusion in the current release cycle (ArcGIS Pro 3.6). The reason this idea hasn't been updated publicly with an "in product plan" status change is because we are treating the defect separate from the idea you posted, which was to add an option to whitelist toolboxes/directories. Status for the idea is what is tracked here.

Feel free to ping us again here if you need another update on the (separate) defect.

[philnagel]

@DrewFlater @HannesZiegler  We have a lot of custom PYT toolboxes that are included in all of our APRX templates and we have noticed some significantly increased initial loading times of the first toolbox in each Pro instance, as compared to previous versions. Wondering if something related to this third-party code detection or something else might have something to do with that? It seems that all of these toolboxes are fully initialized now when the first toolbox is accessed, which I don't believe was the case before.