You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within PAN GUI, we can utilize the global find feature to identify the references of an object. Is there a way to mimic this behavior with pan-os-python?
As a specific example, let's say we have an AddressObject variable "addr" which points to an AddressObject, and we know that this object is referenced in three security PreRules across three different DeviceGroups in our PAN config. How can we obtain the rules in which this AddressObject is used?
In case there is an easier way to accomplish my end goal: I am trying to perform cleanup of duplicate AddressObjects (different names, same value). To do this, I am finding all duplicates, selecting one to keep, and wanting to replace all references of the old duplicate Address with the master address, then delete it. If there is a simpler way to accomplish the end goal, I am open to it.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Within PAN GUI, we can utilize the global find feature to identify the references of an object. Is there a way to mimic this behavior with pan-os-python?
As a specific example, let's say we have an AddressObject variable "addr" which points to an AddressObject, and we know that this object is referenced in three security PreRules across three different DeviceGroups in our PAN config. How can we obtain the rules in which this AddressObject is used?
In case there is an easier way to accomplish my end goal: I am trying to perform cleanup of duplicate AddressObjects (different names, same value). To do this, I am finding all duplicates, selecting one to keep, and wanting to replace all references of the old duplicate Address with the master address, then delete it. If there is a simpler way to accomplish the end goal, I am open to it.
Thanks in advance.
The text was updated successfully, but these errors were encountered: