github.com/PaloAltoNetworks/pango (go): Package pango is a golang cross version mechanism for interacting with Palo Alto Networks devices (including physical and virtualized Next-generation Firewalls and Panorama).  Versioning support is in place for PAN-OS 6.1 and up.  To start, create a client connection with the desired parameters and then initialize the connection:  Initializing the connection creates the API key (if it was not already specified), then performs "show system info" to get the PAN-OS version.  Once the firewall client is created, you can query and configure the Palo Alto Networks device from the functions inside the various namespaces of the client connection.  Namespaces correspond to the various configuration areas available in the GUI.  For example:  Generally speaking, there are the following functions inside each namespace:  These functions correspond with PAN-OS Get, Show, Set, Edit, and Delete API calls.  Get(), Set(), and Edit() take and return normalized, version independent objects.  These version safe objects are typically named Entry, which corresponds to how the object is placed in the PAN-OS XPATH.  Some Entry objects have a special function, Defaults().  Invoking this function will initialize the object with some default values.  Each Entry that implements Defaults() calls out in its documentation what parameters are affected by this, and what the defaults are.  For any version safe object, attempting to configure a parameter that your PAN-OS doesn't support will be safely ignored in the resultant XML sent to the firewall / Panorama.  A PAN-OS configuration can be loaded from a PAN-OS device using `RetrievePanosConfig()` to pull it from a live device or `LoadPanosConfig()` if already in local memory.  Once it's been loaded, use `FromPanosConfig()` for singletons and `AllFromPanosConfig()` for slices of normalized objects from the loaded config.  You can also use this file load and config retrieval to do offline inspection of the config, just make sure to set `pango.Client.Version` to the appropriate PAN-OS version so the version normalization can take place.  The PAN-OS XML API Edit command can be used to both create as well as update existing config, however it can also truncate config for the given XPATH.  Due to this, if you want to use Edit(), you need to make sure that you perform either a Get() or a Show() first, make your modification, then invoke Edit() using that object.  If you don't do this, you will truncate any sub config.  To learn more about PAN-OS XML API, please refer to the Palo Alto Netowrks API documentation.  Functions such as `panos.Client.Set`, `panos.Client.Edit`, and `panos.Client.Delete` take a parameter named `path`.  This path can be either a fully formed XPATH as a string or a list of strings such as `[]string{"config", "shared", "address"}`.  The grand majority of namespaces give their paths as a list of strings, as the XPATH oftentimes needs to be tweaked depending on SET vs EDIT, single objects vs multiple objects, etc, so handling path updates is easier this way.  Example_createAddressGroup is a Panorama example on how to create/delete a security policy with the associated address group and addresses   ExampleCreateInterface demonstrates how to use pango to create an interface if the interface is not already configured.    ExamplePanosInfo outputs various info about a PAN-OS device as JSON.
Keywords: firewall|firewall-configuration|golang|ngfw|paloaltonetworks|panorama|sdk