-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated deployments should be uniquely identifiable with tags #85
Labels
core
New feature or request
Comments
brooke-hamilton
changed the title
automated deployments should be uniquely identifiable
Automated deployments should be uniquely identifiable
Apr 26, 2021
I updated the original text and acceptance criteria to refer to tags instead of resource names. |
brooke-hamilton
changed the title
Automated deployments should be uniquely identifiable
Automated deployments should be uniquely identifiable with tags
Sep 1, 2021
4 tasks
The Terraform portion of this user story is complete |
re-opening because the bicep tagging is not yet completed |
opening once again, still need to complete the bicep portion of this user story |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Benefit/Result/Outcome
Knowing which specific version of MissionLZ was deployed from some automation would benefit development teams and IT Admins.
Description
Tags on resources and resource groups will allow IT Admins and support functions to determine which resources were deployed by MLZ and what version of MLZ was used.
Acceptance Criteria
MissionLandingZoneTF
orMissionLandingZoneARM
?)The text was updated successfully, but these errors were encountered: