-
Notifications
You must be signed in to change notification settings - Fork 517
Document terraform stack deployment modules #2898
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
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
21158b0
to
a84c5d9
Compare
docs/book/how-to/stack-deployment/deploy-a-cloud-stack-with-terraform.md
Outdated
Show resolved
Hide resolved
docs/book/how-to/stack-deployment/deploy-a-cloud-stack-with-terraform.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Alex Strick van Linschoten <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So in general i like this but I feel like there is too much information sort of "dumped" here. The art of writing docs is also to make it consumable and easily digestible for the user. While this is super structured chunks like this can be very daunting for users:

This is when somebody is doing the production guide and it is repeated many places where I feel it comes as a jarring 3-option choice. Before the callout was a single sentence. We should keep it that way, and add the terraform option
That's my feedback :-) Let me know if you'd like to be more specific but I generally think a fresh look at this with the lens of a user who as limited time would help here!
@stefannica id rather say replace "easy cloud deployment wizard" and "easy cloud registration wizard" with "in-browser stack deployment wizard" and "stack registration wizard" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM from my side, though agree that giving people simpler choices (or just one choice) + less text to read is probably the way to go.
@htahir1 done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Please do backport!
* Document terraform stack deployment modules * Apply suggestions from code review Co-authored-by: Alex Strick van Linschoten <[email protected]> * Fix links * Simplified hints * Updated wizard names --------- Co-authored-by: Alex Strick van Linschoten <[email protected]>
@htahir1 backported: https://docs.zenml.io/how-to/stack-deployment/deploy-a-cloud-stack-with-terraform |
Describe changes
Document our newly implemented Terraform stack deployment modules.
Sync-ed with: https://app.gitbook.com/o/-MCl1Hlw9oU4xibZ-ymf/s/sSi8uXbe2nPYIyiHcpxS/how-to/stack-deployment/deploy-a-cloud-stack-with-terraform
Pre-requisites
Please ensure you have done the following:
develop
and the open PR is targetingdevelop
. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.Types of changes