docs: document multi-app porter.yaml and --wait support for addons#340
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: document multi-app porter.yaml and --wait support for addons#340mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Updates the multi-app
porter.yamlandporter applyreference docs to reflect that the multi-app format is now applied automatically (no environment variable required) and that--waitnow also waits for datastore addons to become available before deploying apps.Changes
applications/configuration-as-code/addons-porter-yaml.mdx: removed thePORTER_ADDON_YAML=truerequirement from the usage example and added a section describing--waitbehavior for datastore addons.standard/cli/command-reference/porter-apply.mdx: clarified the--waitflag description and the rollout workflow step to mention addon readiness.Context
The triggering PR routes any multi-app
porter.yaml(top-levelapps:/addons:arrays) through the new apply path by default and extends--waitso that apps which depend on a datastore addon's connection env group don't start rolling out before the datastore is ready.cc @GKestenberg for review.