Generate configuration names and config.vars files#53
Merged
Conversation
This was
linked to
issues
Mar 2, 2021
brooke-hamilton
approved these changes
Mar 2, 2021
jwaltireland
pushed a commit
to ARPA-H/AzureMissionLZ
that referenced
this pull request
Nov 14, 2024
* add a config folder to centralize generation
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.
Description
Previously, the names of Mission LZ and individual terraform configuration resources (the resource groups that store terraform state, and the Service Principal and Key Vault that permits access to the subscriptions) were known only at resource creation time.
This change allows us to derive these names at any time given a
mlz_tf_cfg.varfile and aide in CI/CD efforts, or any other post-configuration deployment activity.Issue reference
The issue this PR is associated with: #54
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:
shellcheck.vscode/extensions.json.)