-
Notifications
You must be signed in to change notification settings - Fork 676
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
ibm_cloud_shell_account_settings delete issue #3242
Labels
service/IBM Cloud Shell
Issues related to Cloud Shell
Comments
I figured it out, the issue is the "rev" parameter, the initial apply and destroy do not need the |
Hi @jpmonge86, Thanks for helping to figure this out, I'll create a task to get it updated. |
Thanks @seancallanan for helping me debug the issue |
kavya498
added a commit
to kavya498/terraform-provider-ibm
that referenced
this issue
Oct 26, 2021
kavya498
added a commit
to kavya498/terraform-provider-ibm
that referenced
this issue
Oct 26, 2021
hkantare
pushed a commit
that referenced
this issue
Oct 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Community Note
Terraform CLI and Terraform IBM Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Expected Behavior
Resource destruction to be successful.
Actual Behavior
Resource hangs and it never gets destroyed.
Steps to Reproduce
terraform apply
> this works ok the first timeterraform destroy
> this works ok the first time tooterraform apply
> the subsequent applies fail no matter what one does, it is almost like the first destroy corrupts the target and then the system fails to apply changes.The text was updated successfully, but these errors were encountered: