Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken / Incorrect links in Operationalize Guide #606

Open
bgpanw opened this issue Jul 13, 2021 · 1 comment
Open

Broken / Incorrect links in Operationalize Guide #606

bgpanw opened this issue Jul 13, 2021 · 1 comment

Comments

@bgpanw
Copy link

bgpanw commented Jul 13, 2021

What? Broken / incorrect HTTP links "Prisma Cloud Operationalize Guide (Compute)" Last Revised, June 18th 2021
Where? Multiple sections

page 13 , in the bottom section of the page is a list of HTTP links:
"
Resources:
• Install articles
• Upgrading Prisma Cloud
• High availability
• Disaster recovery
• Integrating with Active Directory, OpenLDAP, or SAML.
• Projects
• Air-gapped environments
• Automation with the API and twistcli
"

None of them go to any unique article or helpful part of documentation which goes into those specific topics in detail.
All of them currently resolve to the main page of the administrators guide although they originally targeted something specific.

The resulting page is: https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute

Update 7/14:
Similar problems were found on page 14 of the same document for the deploy http links, all going to the homepage of the admin guide instead of linking to the individual install guides for each platform:

"
Deploy
After completing the planning phase, deploying Prisma Cloud is pretty easy. Refer to one of our dedicated install guides for Kubernetes, OpenShift, Pivotal Container Service, Docker Swarm, Amazon ECS, DC/OS, and Windows.
"

@sgordon46
Copy link
Collaborator

@iansk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants