NGINXaaS: add docs for Secret Manager integration #1675
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This moves the "Identity and access management" page to be under the "Getting started" section because it no longer applied to just logging and monitoring. Luckily, the page's URL is already under getting-started, so that did not need to change. This also updated the page's contents to add instructions to allow fetching secrets from Secret Manager.
NGINXaaS can now fetch secrets from Secret Manger. This adds instructions on how to integrate with Secret Manager and use secrets as certificates for NGINX configurations.
github-actions
bot
added
the
documentation
✅ Deploy Preview will be available once build job completes!
|
valyria257
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
NGINXaaS can now fetch secrets from Secret Manger. This adds
instructions on how to integrate with Secret Manager and use
secrets as certificates for NGINX configurations.
This moves the "Identity and access management" page to
be under the "Getting started" section because it no
longer applied to just logging and monitoring. Luckily,
the page's URL is already under getting-started, so that
did not need to change.
This also updated the page's contents to add instructions
to allow fetching secrets from Secret Manager.
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. ↩