-
Notifications
You must be signed in to change notification settings - Fork 187
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
When docker service need to be replaced but not destroy exists one #574
Comments
I would be delighted to know if anyone has a workaround for this. In our CI/CD pipeline, when this occurs, just about the only thing I can do to handle it in an automated way is to destroy everything in the stack and recreate it which feels like an incredibly blunt instrument. |
No workaround, but I believe that the reasoning of #152 was only valid for containers, but is not for services as they update labels in-place just fine - at least on the resource level in my case. Maybe using the
on the resource level works for you @matthewbaggett though this should anywayse be the default. 🤷 |
Community Note
Terraform (and docker Provider) Version
Affected Resource(s)
docker_service
Terraform Configuration Files
Debug Output
Panic Output
Expected Behaviour
The
docker_service
should be destroyed first and replaced with a new one.Actual Behaviour
The
docker_service
is created directly that got name conflict.Steps to Reproduce
Important Factoids
Heavily depend on the customize module which generated a lot of default config.
References
N/A
The text was updated successfully, but these errors were encountered: