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

Add tag for resource groups #7811

Closed
wants to merge 1 commit into from
Closed

Conversation

vnguyen7
Copy link
Contributor

@vnguyen7 vnguyen7 commented Mar 5, 2019

Add tags for resource group related to #7109 in order to fix from PR #7774 of joestump. (one last test )

@ghost ghost added size/M Managed by automation to categorize the size of a PR. service/resourcegroups Issues and PRs that pertain to the resourcegroups service. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. documentation Introduces or discusses updates to documentation. labels Mar 5, 2019
@@ -176,3 +216,45 @@ func resourceAwsResourceGroupsGroupDelete(d *schema.ResourceData, meta interface

return nil
}

func tagsToMapRG(ts map[string]interface{}) map[string]string {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can reuse the functionality in tagsGeneric.go here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many thanks !!!! Good to know since I'm struggle with the Tag function !!

@bflad
Copy link
Contributor

bflad commented Mar 6, 2019

Hi @vnguyen7 👋There is a previously opened pull request for this functionality: #7774. In the situation, the maintainers would prefer if you worked with the previous contributor by either including their contributions, commenting/reviewing their contribution, or discussed with them using this pull request instead. Thanks for your understanding as we try to respect all contributions.

@bflad bflad added the enhancement Requests to existing resources that expand the functionality or scope. label Mar 6, 2019
@vnguyen7
Copy link
Contributor Author

vnguyen7 commented Mar 6, 2019

@bflad Hi apologize about that. I just edited in order for #7774's credit.

@DrFaust92
Copy link
Collaborator

Hey @vnguyen7, i have a working PR (#10640) for this with changes including the keyvaluetags package, would you like me to merge these to this PR or close this one?

@bflad
Copy link
Contributor

bflad commented Nov 19, 2019

Hi @vnguyen7 👋 Thank you for working on this and sorry it was previously lingering.

As @DrFaust92 is mentioning above, there have been some consistency changes and simplifications to how to implement resource tagging into the Terraform AWS Provider codebase, which can be found in the Contributing Guide using a new internal keyvaluetags package.

Since we didn't see a response to the above and we would prefer to implement the newer methodology, we are going to opt to close this. Thanks again for your contribution here and let us know if you have any questions.

@bflad bflad closed this Nov 19, 2019
@ghost
Copy link

ghost commented Mar 29, 2020

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!

@ghost ghost locked and limited conversation to collaborators Mar 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Introduces or discusses updates to documentation. enhancement Requests to existing resources that expand the functionality or scope. service/resourcegroups Issues and PRs that pertain to the resourcegroups service. size/M Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants