-
Notifications
You must be signed in to change notification settings - Fork 119
feat: Update WAF install and configuration steps #1296
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
Conversation
This commit adds a necessary signature command to Alpine Linux, Debian & Ubuntu installation steps. It further improves installation use cases by adding some troubleshooting guidance to post-installation checks. Similarly, policy and bundle-specific troubleshooting guidance has been added to the compiler page. Finally, information on Bot signatures has been added, with contextual links added or updated for logical connections between use cases.
✅ Deploy Preview will be available once build job completes!
|
Can you comment in the AC for the PR that the updated installation steps were tested and verified? Any time an install guide is updated, we should verify the changes -- installation is a first impression. |
Co-authored-by: Jon Torre <[email protected]>
@travisamartin I have confirmation of the installation step changes working from a principal solutions engineer who tested it in a lab, though I am waiting for word back from an active customer case to double-confirm it. |
Proposed changes
This commit adds a necessary signature command to Alpine Linux, Debian &
Ubuntu installation steps. It further improves installation use cases by
adding some troubleshooting guidance to post-installation checks.
Similarly, policy and bundle-specific troubleshooting guidance has been
added to the compiler page. Finally, information on Bot signatures has
been added, with contextual links added or updated for logical
connections between use cases.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩