-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Add Tag Support to Resource Group Resource #10640
Add Tag Support to Resource Group Resource #10640
Conversation
Hi @DrFaust92 👋 Thanks for submitting this one as well. Looks like there's a bit of a backlog for adding tagging for this resource. The maintainers prefer working with contributions in their submission order to be fair to contributors. In this case, that means we should try working with the original author (even before #7811 there is #7774) to either help review their contribution, asking them to close their contribution, or if they are unresponsive to submit a fix on top of their commits unless they close their pull request so they receive contributing credit. Before we even go through that though, it might be best to get the Please reach out with any questions. |
@bflad, ill open up a separate PR for the |
b2da7d3
to
f2f4d09
Compare
fixed merge conflicts
|
Please, merge it! |
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.
Looks good, thanks @DrFaust92 🚀
Output from acceptance testing:
--- PASS: TestAccAWSResourceGroup_basic (14.51s)
--- PASS: TestAccAWSResourceGroup_tags (20.03s)
var v resourcegroups.Group | ||
resourceName := "aws_resourcegroups_group.test" | ||
n := fmt.Sprintf("test-group-%d", acctest.RandInt()) | ||
desc1 := "Hello World" |
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.
Nit: This acceptance testing does not need to verify anything with this attribute, so it should omitted or hardcoded in the test configurations.
|
||
resource_query { | ||
query = <<JSON | ||
%s |
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.
Nit: We prefer to hardcode values like these into the test configurations so they can more easily be copy-pasted for manual Terraform CLI usage.
This has been released in version 2.39.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Closes #7109
Release note for CHANGELOG:
Output from acceptance testing:
I saw that there is pending PR for this #7811 which i only realised only after i was done with this.
this refactors the tests as well as uses the keyvaluetags lib