-
Notifications
You must be signed in to change notification settings - Fork 55
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
feat: Ignore tags #6823
feat: Ignore tags #6823
Conversation
@@ -10,7 +10,7 @@ locals { | |||
management_tags = { | |||
prime-app = "simple-report" | |||
environment = local.env | |||
resource_group = "${local.project}-${local.name}-${local.env}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was incorrectly tagged. "${local.project}-${local.name}-${local.env}"
resolves to prime-simple-report-dev3
when it should have been prime-simple-report-dev
.
6be9d03
to
c84b1d8
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🏷️ 💥 ❗
Is the cdc tagging our resources outside of terraform / source control? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🏷️ ➡️ 🗑️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
DEVOPS PULL REQUEST
Related Issue
Changes Proposed
resource_group
tag to be based ondata.azurerm_resource_group.dev.name
instead of"${local.project}-${local.name}-${local.env_level}"
or"${local.project}-${local.name}-${local.env}"
. This brings consistency across all environment configs as some were usinglocal.env
which would tag dev(2,3,4,5...) incorrectly. By making this update, we can reduce some future mental overhead when reading through the code to understand which resource group a resource belongs to. I'll call out an example inline on adev3
file where this caused an inconsistency.Testing
Checklist for Primary Reviewer
Infrastructure
terraform-plan
job inside the "Terraform Checks" workflow run for this PR. Confirm that there are no unexpected changes!Security
Cloud
test
,dev
, orpentest
environment for verificationDocumentation