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
I'm using the vault provider and before destroying the vault_database_secret_backend_static_role I want to revoke all leases using an API call. (I achieve this using a local-exec provider. Long story short: The command contains reference to self.triggers.xyz which I see in the tfstate, but IMO doesn't resolve properly. I have simplified the use case to the following:
Thanks for reporting this! You are correct that the self reference should still work for the destroy time provisioner.
I verified this is working in master, and will be fixed in the next 0.13 development release.
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
Aug 20, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
v0.13Issues (primarily bugs) reported against v0.13 releases
Issue
vault_database_secret_backend_static_role
I want to revoke all leases using an API call. (I achieve this using alocal-exec
provider. Long story short: The command contains reference toself.triggers.xyz
which I see in thetfstate
, but IMO doesn't resolve properly. I have simplified the use case to the following:Expected behavior:
Actual behavior:
Error: local-exec provisioner command must be a non-empty string
Terraform Version
Debug Output
Gist
Steps to Reproduce
terraform init
terraform apply
terraform destroy
References
I found the following ticket, which points out, that this shoud be the recommended way to work with variables from on-destroy local-exec resources.
The text was updated successfully, but these errors were encountered: