Skip to content
This repository has been archived by the owner on Dec 5, 2020. It is now read-only.

Missing Delete Action for Chef Environment Provider #5

Open
hashibot opened this issue Jun 13, 2017 · 1 comment
Open

Missing Delete Action for Chef Environment Provider #5

hashibot opened this issue Jun 13, 2017 · 1 comment

Comments

@hashibot
Copy link

This issue was originally opened by @rb1whitney as hashicorp/terraform#11805. It was migrated here as part of the provider split. The original body of the issue is below.


I am requesting that we add the missing delete function for chef_environment. Per the code in: https://github.com/hashicorp/terraform/blob/master/vendor/github.com/go-chef/chef/environment.go, there is mention of a delete function. Is it possible to have this missing feature implemented? When you provision a chef_environment with chef nodes, the chef environment sticks around and causes issues if the environment is re-created. I was able to monkey patch this issue locally by just copying the logic from client.go and renaming client to environment (to hit the right rest api for chef) and would like to see it fixed in future versions if possible.

Terraform Version

0.8.6

Affected Resource(s)

Please list the resources as a list, for example:

  • chef_environment

Expected Behavior

Chef Environment should be able to delete resource when calling terraform destroy

Actual Behavior

Nothing happens since chef_environment is missing a delete function

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:
0. terraform apply

  1. terraform destroy

References

None

@hynd
Copy link

hynd commented Mar 21, 2018

Destroying a chef_environment works as expected for me.

$ terraform version
Terraform v0.11.4
+ provider.chef v0.1.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants