Skip to content
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

Recreate Rancher stack if it was removed #11539

Merged
merged 1 commit into from
Jan 31, 2017
Merged

Recreate Rancher stack if it was removed #11539

merged 1 commit into from
Jan 31, 2017

Conversation

raphink
Copy link
Contributor

@raphink raphink commented Jan 31, 2017

Currently, a stack that is manually removed on Rancher is never seen as removed by Terraform, and thus not recreated. This patch forces Terraform to recreate a removed stack.

@stack72
Copy link
Contributor

stack72 commented Jan 31, 2017

LGTM! Thanks for the work - ignore the build failure here! We have an issue with one of the unit tests for remote state that isn't affected by this change

Paul

@stack72 stack72 merged commit 2914a38 into hashicorp:master Jan 31, 2017
@mcanevet
Copy link
Contributor

@stack72 will/could this be backported to 0.8-stable? Or do we have to wait for 0.9?

@stack72
Copy link
Contributor

stack72 commented Jan 31, 2017

@mcanevet this will be in 0.8.6

@mcanevet
Copy link
Contributor

great! thanks

arcadiatea pushed a commit to ticketmaster/terraform that referenced this pull request Feb 9, 2017
@ghost
Copy link

ghost commented Apr 17, 2020

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 ghost locked and limited conversation to collaborators Apr 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants