refactor 'provisioners' content #699
Open
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
Vercel Previews Deployed
|
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.
This PR merges the non-reference content for using provisioners into a single usage page. It also combines guidance on using alternatives to provisioners. The resulting topic is about performing post-apply operations. Note that I kept the file name
provisioners.mdxfor a few reasons:I added a redirect and tried to fix all links, but we will need to take another pass after all of the content has been merged to the rollup branch.
For this review, just look for copy errors and obvious content problems. During the draft phase, there were a lot of technical questions. In some cases, I was able to address them all. In others, I reverted to original text on the assumption that if it was already there it had been verified in the past.