PaloAltoNetworks / PaloAltoNetworks/pan.dev
Support API
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 78
- Forks
- 88
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 18
Description
Is your feature request related to a problem?
It would be incredibly helpful for PAN to provide an API endpoint to collect data that is otherwise not available in an automated fashion. For example, https://live.paloaltonetworks.com/t5/customer-resources/pan-os-globalprotect-amp-user-id-preferred-release-guidance-from/ta-p/258304 or https://www.paloaltonetworks.com/services/support/end-of-life-announcements/end-of-life-summary
Describe the solution you'd like
A set of REST endpoints that allow for calls similar to:
GET /api/v0/support/pan-os/releases- This would list all releases for PAN-OS, their "recommended" status, their in-support and EoS dates.
GET /api/v0/support/pan-os/releases/<version number>- This would list the same as above but for a specific version number.
GET /api/v0/support/ngfw/<model>- This would return the release date, and EoL dates (standard and extended) for a given model
Alternatively endpoints whereby parameter filters could be used to collect this info would work as well.
GET /api/v0/support/products?category=ngfw&model=<model number> - This would cover any product, and could be sortable
GET /api/v0/support/releases?category=pan-os&recommended=true - Gives you recommended only PAN-OS releases.
Could combine the 2 in case there are specific releases not elligible for a given device.
Describe alternatives you've considered
Perhaps a published JSON file that could be accessed through a standard web request and parsed client side would work as well
Additional context
My specific requirement is finding a way to populate software versions and their support information into a DCIM / Network Source of Truth system like NetBox or Nautobot without having to do it manually.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not identify repository files, tests, or an implementation entry point. Start by locating the existing API structure and determining where support and product data could come from; done means an agreed endpoint or published JSON interface provides the requested release, recommendation, and lifecycle information.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100