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

RDS resource not resolving KMS Alias on subsequent plans #15883

Closed
cfromm1911 opened this issue Aug 23, 2017 · 3 comments
Closed

RDS resource not resolving KMS Alias on subsequent plans #15883

cfromm1911 opened this issue Aug 23, 2017 · 3 comments
Labels
provider/aws question waiting-response An issue/pull request is waiting for a response from the community

Comments

@cfromm1911
Copy link

If I create an RDS instance and reference a KMS key via Alias ARN, the instance is created and properly refers to the Alias' target. However, on subsequent plans, this forces perpetual recreation, as the ARN in state (the alias arn) does not match the ARN on the instance (the key arn).

Refreshing state should resolve the Alias before comparing to existing instance. This would allow Aliases to be usable on RDS resources.

@tombuildsstuff
Copy link
Contributor

Hey @wv-cfromm

Thanks for opening this issue - would it be possible to share the Terraform configuration you're using so that we can take a look into this?

Thanks!

@tombuildsstuff tombuildsstuff added the waiting-response An issue/pull request is waiting for a response from the community label Aug 23, 2017
@hashibot
Copy link
Contributor

This issue has been automatically migrated to hashicorp/terraform-provider-aws#1477 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.

@ghost
Copy link

ghost commented Apr 7, 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 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
provider/aws question waiting-response An issue/pull request is waiting for a response from the community
Projects
None yet
Development

No branches or pull requests

3 participants