-
Notifications
You must be signed in to change notification settings - Fork 102
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 support to terraform import tls_private_key resource #44
Comments
This would be super useful, but in the meantime, my work-around for terraform 0.11.13:
This is obviously super tedious and could easily be simplified with a tiny script, but since I don't intend on doing this frequently, the time to write and test the script far exceeds the time it takes to edit a few JSON values by hand. |
Is this enhancement on the roadmap? |
Hi @Marcus-James-Adams 👋 The Terraform Core Team are actively developing a new and improved import workflow. We will revisit issues and PRs relating to modifying behaviour of import in the utility providers (including tls) once the new import workflow has been implemented in Terraform Core. |
Hello. Is there any update on this? |
Another good reason to implement this is terraform-aws-provider, currently |
This issue was originally opened by @trajano as hashicorp/terraform#20729. It was migrated here as a result of the provider split. The original body of the issue is below.
Current Terraform Version
Use-cases
I want to use Terraform as a replacement for XCA to manage the certificates, but I don't want to generate new keys. I do not want to use
data
as it refers to existing data files for the keys instead I want them to be managed within Terraform state itself.Attempted Solutions
Proposal
References
The text was updated successfully, but these errors were encountered: