PaloAltoNetworks / PaloAltoNetworks/pan.dev
Issue/Help with "Move a security rule"
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 78
- Forks
- 88
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 18
Description
Documentation link
Describe the problem
I am referring to pan.dev (link below), but it appears that this page does not contain the correct information to begin with.
For example, the following incorrect information/behavior is observed
- The request method is listed a POST, but the Python sample script shows GET.
- QueryParameters requires a 'folder', but the Python sample script is not updated at all even if the 'folder' is specified in the field for creating a REQUEST.
pan.dev Move a security rule (https://pan.dev/access/api/prisma-access-config/post-sse-config-v-1-security-rules-id-move/)
Also, the API endpoint is described as requiring the ID of the security rule to be moved to be added to the URL, but when a request is actually sent to the endpoint that specifies the ID of the security rule, it results in a "404 NotFound".
The security rule ID used to confirm the above behavior are the ID of the security rules that actually exist, and the IDs are never incorrect.
The following is the API response result when request to this api endpoint
== API Responses ========
Response: {
"statusCode": 404,
"error": "Not Found",
"message": "Not Found",
"errorCode": "Not Found",
"errorMessage": "Not Found",
"httpStatusCode": 404,
"ok": false,
"trackingId": "6fe24d0b-5c5c-48c2-aee1-20b966ad48b0"
}
Suggested fix
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
Start with the linked pan.dev “Move a security rule” page and compare its documented POST method, folder query parameter, and Python sample. Reproduce the reported request with an existing security rule ID, then update the documentation if the endpoint behavior is confirmed and verify that the example and response details are consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100