Skip to content
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

Closed
glennmusa opened this issue Mar 18, 2021 · 4 comments · Fixed by #422 or #432
Closed

Automated deployments should be uniquely identifiable with tags #85

glennmusa opened this issue Mar 18, 2021 · 4 comments · Fixed by #422 or #432
Assignees
Labels
core New feature or request

Comments

@glennmusa
Copy link
Contributor

glennmusa commented Mar 18, 2021

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

  • A tag identifies resources deployed by Mission Landing Zone, e.g. "MissionLandingZone"
  • Resources deployed via Terraform are distinct from those deployed with Bicep (maybe MissionLandingZoneTF or MissionLandingZoneARM?)
  • Resource groups receive the same tags
@brooke-hamilton brooke-hamilton added the core New feature or request label Mar 26, 2021
@brooke-hamilton brooke-hamilton changed the title automated deployments should be uniquely identifiable Automated deployments should be uniquely identifiable Apr 26, 2021
@brooke-hamilton
Copy link
Contributor

I updated the original text and acceptance criteria to refer to tags instead of resource names.

@brooke-hamilton brooke-hamilton changed the title Automated deployments should be uniquely identifiable Automated deployments should be uniquely identifiable with tags Sep 1, 2021
@lisamurphy-msft
Copy link
Contributor

The Terraform portion of this user story is complete
Pending Bicep tagging before resolution

@lisamurphy-msft
Copy link
Contributor

re-opening because the bicep tagging is not yet completed

@lisamurphy-msft
Copy link
Contributor

opening once again, still need to complete the bicep portion of this user story

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core New feature or request
Projects
None yet
3 participants