You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to add a do_not_destroy argument to the local_file configuration item so that when terraform destroy is executed the generated local file is left intact? The reason? I create dynamic content for a post-destroy Ansible script and it would be useful to keep the content of the locally-generated file for this playbook.
i.e. would it be acceptable to provide the ability to do this...
This issue has been automatically migrated to hashicorp/terraform-provider-local#7 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.
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
locked and limited conversation to collaborators
Apr 5, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Would it be possible to add a
do_not_destroy
argument to thelocal_file
configuration item so that whenterraform destroy
is executed the generated local file is left intact? The reason? I create dynamic content for a post-destroy Ansible script and it would be useful to keep the content of the locally-generated file for this playbook.i.e. would it be acceptable to provide the ability to do this...
With the above if
terraform apply
is re-excuted is is perfectly fine (and expected) to over-write any existing file.Terraform Version
Terraform Configuration Files
Debug Output
n/a
Crash Output
n/a
Expected Behavior
n/a
Actual Behavior
n/a
Steps to Reproduce
n/a
Additional Context
n/a
References
n/a
The text was updated successfully, but these errors were encountered: