NGINXaaS: Address missing info and points of user friction #1588
+14
−8
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
github-actions
bot
added
the
documentation
✅ Deploy Preview will be available once build job completes!
|
puneetsarna
commented
Dec 16, 2025
amudukutore
reviewed
Dec 17, 2025
content/nginxaas-google/getting-started/create-deployment/deploy-console.md
Outdated
Show resolved
Hide resolved
amudukutore
reviewed
Dec 17, 2025
amudukutore
reviewed
Dec 17, 2025
amudukutore
approved these changes
Dec 17, 2025
There was a problem hiding this comment.
@puneetsarna - Thanks for (quickly) addressing these docs issues and making these changes. I had a few minor suggestions and will leave it up to you whether you want to use them or not. Approving these regardless.
I created issue https://gitlab.com/f5/nginx/nginxaas/gcp-tracking/-/issues/916 to track this work (it's assigned to you).
puneetsarna
force-pushed
the
ps-dev-docs
branch
2 times, most recently
from
024c513 to
a9eea9a
Compare
amudukutore
approved these changes
Dec 17, 2025
This makes it easier for the user to know what it looks like when we are asking them to save it for use later on in the deployment.
This is important as we do not have references to it anywhere and is information needed by the user to set up deployment observability.
After I am done setting up my WIF provider, I should be directed to enable monitoring and logging for my deployment.
We want to strongly recommend using a connection preference that is secure but keep the instructions open for a user that may not be as concerned with security or just wants to prioritize deploying quickly just to try out the service.
puneetsarna
force-pushed
the
ps-dev-docs
branch
from
a9eea9a to
a2c7c1d
Compare
travisamartin
approved these changes
Dec 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
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. ↩