Automation/API Discussions

Resolved! panos remove address object script messes up the device group setup.

Hi All,

So far I'm getting the hang of python panos, which allows me to connect via panorama to make changes and push to firewalls. I've been able to create address objects and modify contents of address groups and security rules with no issues.

Recent

Resolved! pandevice newbie issues with fetching objects (addressobject, addressgroup, serviceobject...

Hello,

I'm not pretending to be a pandevice guru... moreover, I'm not pretending to be python guru. Rather basic skills in both. I've got a task to retrieve firewall configuration (rules + object definitions) from two datacenters (primary & DR, separ

Resolved! Add existing local User to existing User Group

Hi all - I've been stuck trying to figure out a way to fix an issue I'm having while running this task in Ansible:

Resolved! policy rules hit count from API

I am trying to figure out how to get the hit count for rules via the REST API. 

I used the REST API browser and found that the URI path is

.

However when I ru

Resolved! Modify GlobalProtect Device Block List via API

I am trying to automate blocking GlobalProtect clients via API calls. Our firewall is running PanOS 9.1.15-h1 and is controlled by a onsite Panorama instance on 10.1.8-h2. Due to the version mismatch GlobalProtect device blocks must be implemented di

Resolved! Terraform object in multiple Panorama Address Groups

I have a use case for being able to apply set objects (address, service, etc. ) across multiple Panorama device groups in 3 Panorama appliances. How can I do that by defining each of object only once? 

The object only allows a single device group ref

Resolved! PAN-OS SDK Device Group Hierarchy

Is there a way to create device under a parent or move a device group using the sdk. 

Similar to Operational command:

> request move-dg dg1 new-parent-dg dg1_parent create-dg yes

I am aware of the dg_hierarchy opstate, which helps finding the device gr

Resolved! Cortex API (get_alerts) Error 'Got an invalid input while processing XDR public API'

I was able to use "get_endpoints" because in that instance, the PARAMS are just {}.

But with /public_api/v1/alerts/get_alerts/ :

>>> PARAMS = {"request_data": {"filters": [{"field": "alert_id_list","operator": "in","value": [88299]}]}}
>>> r = request