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

Q: Workaround for computed resource output as shared key? #65

Closed
naseemkullah opened this issue Apr 26, 2022 · 3 comments
Closed

Q: Workaround for computed resource output as shared key? #65

naseemkullah opened this issue Apr 26, 2022 · 3 comments

Comments

@naseemkullah
Copy link

it cannot use a computed resource output (e.g. random_password.my_shared_key.result) as input for the shared key

Is this an anti-pattern or should the module be able to support that?

@naseemkullah
Copy link
Author

It probably makes sense to always store any computed resource ouput password as a secret outside of terraform and then use a data source.

@antonbabenko
Copy link
Member

There is a long-standing issue in Terraform - hashicorp/terraform#4149 - which means that users need to create such resources in advance using -target and then run terraform apply to create the rest of resources.

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants