Skip to content

Generate configuration names and config.vars files#53

Merged
glennmusa merged 9 commits intomainfrom
glennmusa/generatenames
Mar 3, 2021
Merged

Generate configuration names and config.vars files#53
glennmusa merged 9 commits intomainfrom
glennmusa/generatenames

Conversation

@glennmusa
Copy link
Copy Markdown
Contributor

@glennmusa glennmusa commented Mar 2, 2021

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.var file 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:

  • Code compiles or validates correctly
  • BASH scripts have been validated using shellcheck
  • All tests pass (manual and automated)
  • The documentation is updated to cover any new or changed features
  • Markdown files have been linted using the recommended linter. (See .vscode/extensions.json.)
  • Relevant issues are linked to this PR

@glennmusa glennmusa merged commit 95d631f into main Mar 3, 2021
@glennmusa glennmusa deleted the glennmusa/generatenames branch March 3, 2021 01:27
jwaltireland pushed a commit to ARPA-H/AzureMissionLZ that referenced this pull request Nov 14, 2024
* add a config folder to centralize generation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

I need to derive the MissionLZ resource names given a MissionLZ configuration file

4 participants