Add multi-environment example #203
Merged
Conversation
This file contains 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
GrantBirki
reviewed
Sep 6, 2023
GrantBirki
reviewed
Sep 6, 2023
| if: ${{ needs.start.outputs.continue == 'true' }} | ||
|
|
||
| # Use the environment specified by the `.noop` or `.deploy` comment. | ||
| environment: ${{ needs.start.outputs.environment }} |
There was a problem hiding this comment.
This is extremely clever! I love it 🚀
There was a problem hiding this comment.
Being able to do this potentially changes the entire approach to using this Action for a lot of flexibility. This is wild! Thank you 🌟
Co-authored-by: Grant Birkinbine <grant.birkinbine@gmail.com>
GrantBirki
approved these changes
Sep 6, 2023
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 adds a new multi-job example that shows how separate environments can be used to start/stop the branch-deploy process and perform the actual deployment.
The original need that resulted in this approach was being able to deploy to multiple Azure environments using Terraform. In particular, each environment was located on a separate tenant/subscription, hence the need for different credentials, Terraform workspaces, etc. Originally, I tried writing this to use only a
secretsenvironment as mentioned in the README, but the workflow ended up with a lot of additional fluff to simply choose the right secrets/variables. I left in a fair bit of detail, so please feel free to remove anything that might be extraneous.Also: Prettier automatically formatted some of the other examples. I did confirm that nothing was changed functionally.
I'd be happy to hear any feedback!