Allow destroy-time provisioners to access variables

<!-- Hi there, Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html. If your issue relates to a specific Terraform provider, please open it in the provider's own repository. The index of providers is at https://github.com/terraform-providers . --> ### Current Terraform Version <!--- Run `terraform -v` to show the version, and paste the result between the ``` marks below. This will record which version was current at the time of your feature request, to help manage the request backlog. If you're not using the latest version, please check to see if something related to your request has already been implemented in a later version. --> ``` Terraform v0.12.18 ``` ### Use-cases <!--- In order to properly evaluate a feature request, it is necessary to understand the use-cases for it. Please describe below the _end goal_ you are trying to achieve that has led you to request this feature. Please keep this section focused on the problem and not on the suggested solution. We'll get to that in a moment, below! --> Using a local-exec provisioner when=destroy in a null resource, to remove local changes; currently, the setup provisioner has: ```interpreter = [var.local_exec_interpreter, "-c"]``` ### Attempted Solutions <!--- If you've already tried to solve the problem within Terraform's existing features and found a

Posted by shaunc on Dec 14, 2019, 7:38 PM

Tags

• onboarding (E-commerce)

Related issues

• Some other ones to add on from my fresh install: Start menu search will search the Microsoft Store for apps they want you to install, som...
• New Release?
• 【Not An Issue But Tutorial】A complete tutorial of pre-processing steps
• Meta issue: plugin system
• Accept `Json` field paths when trying to order by `Json` field
• proposal: cmd/go: allow versioned `go build` commands