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

provider/aws: Add KMS key tag support #12243

Merged
merged 2 commits into from
Mar 17, 2017
Merged

provider/aws: Add KMS key tag support #12243

merged 2 commits into from
Mar 17, 2017

Conversation

ewbankkit
Copy link
Contributor

@ewbankkit ewbankkit commented Feb 24, 2017

Add support for AWS KMS key tagging.
Acceptance test:

make testacc TEST=./builtin/providers/aws/ TESTARGS='-run=TestAccAWSKmsKey_tags'

Additional KMS API actions:

  • ListResourceTags
  • TagResource
  • UntagResource

@ewbankkit
Copy link
Contributor Author

Added acceptance test and rebased.

@ewbankkit ewbankkit changed the title [WIP] provider/aws: Add KMS key tag support provider/aws: Add KMS key tag support Feb 24, 2017
@stack72
Copy link
Contributor

stack72 commented Feb 28, 2017

Hi @ewbankkit

What do you suggest we do about the permissions issue?

Paul

@ewbankkit
Copy link
Contributor Author

@stack72 I would say just note in the CHANGELOG. The documentation doesn't currently state which IAM permissions are required for which resources and I'm sure this situation (additional attributes imply additional permissions) happens relatively frequently.
Maybe once you get to 1.0 we'll have to worry more about such changes.

Copy link
Member

@radeksimko radeksimko left a comment

Choose a reason for hiding this comment

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

Other than the error handling, this overall looks 👌 and I'm happy to merge it once that is addressed.

KeyId: metadata.KeyId,
})
if err != nil {
return nil
Copy link
Member

Choose a reason for hiding this comment

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

As mentioned in #12137 (comment) we should not be ignoring the error here. Instead to avoid confusions you can do something similar to what I did in #12759 - i.e. make the error message descriptive enough.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agreed. I'll try and fix that today.

@ewbankkit
Copy link
Contributor Author

@radeksimko Made change as suggested (and rebased). I think the initial return nil was a typo for return err but still agree on better error message.

@radeksimko radeksimko merged commit bf02d5a into hashicorp:master Mar 17, 2017
@ewbankkit ewbankkit deleted the aws_kms_key-tags branch March 17, 2017 20:59
@cblecker cblecker mentioned this pull request Mar 18, 2017
@ghost
Copy link

ghost commented Apr 15, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants