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

Feature request: Cross-account Route53 Zone Association #22780

Closed
jeffb4 opened this issue Sep 12, 2019 · 3 comments
Closed

Feature request: Cross-account Route53 Zone Association #22780

jeffb4 opened this issue Sep 12, 2019 · 3 comments

Comments

@jeffb4
Copy link
Contributor

jeffb4 commented Sep 12, 2019

Current Terraform Version

$ terraform -v
Terraform v0.12.8
+ provider.aws v2.25.0
+ provider.helm v0.10.2
+ provider.kubernetes v1.9.0
+ provider.local v1.3.0
+ provider.null v2.1.2
+ provider.rancher2 v1.4.1
+ provider.random v2.2.0
+ provider.template v2.1.2

Use-cases

We are defining an internal Route53 Zone in Terraform and need to share it with another account to which we peer a VPC. That currently requires the use of an exec provisioner and the awscli

Attempted Solutions

There is no pattern that I would expect to do this association with existing Terraform AWS resources. For a solution I used an exec provisioner.

Proposal

Something similar to the cross-account peering resources provided by Terraform would work for this.

References

#10208 - original request, closed for some reason
#11174 - dup of above
#12465 - same thing in bugrep format

@rrijkse
Copy link

rrijkse commented Sep 12, 2019

This should be opened in the AWS provider issue tracker. It looks similar to this issue over there: hashicorp/terraform-provider-aws#9453

@jeffb4
Copy link
Contributor Author

jeffb4 commented Sep 12, 2019

Thanks!

@jeffb4 jeffb4 closed this as completed Sep 12, 2019
@ghost
Copy link

ghost commented Oct 13, 2019

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 Oct 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants