-
-
Notifications
You must be signed in to change notification settings - Fork 693
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
docker-build declares its own provider and therefore cannot be easily deleted #267
Comments
This issue has been automatically marked as stale because it has been open 30 days |
This issue was automatically closed because of stale in 10 days |
Re-open this issue. Still a very frustrating issue I deal with regularly. |
I can confirm that this is quite confusing. |
I don't know what I was thinking about while making this, so I will fix this tomorrow :) |
This issue has been resolved in version 3.2.1 🎉 Today is better than tomorrow! |
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. |
Description
The docker-build submodule declares its own docker provider. This means that if I create an instance of this module and later try to delete it,
terraform plan
will fail with an error like this:This doesn't play well with CI pipelines as the only way to fix this is to manually run
terraform state rm
. Can you instead tell users to properly declare their docker provider in their root module instead?See https://stackoverflow.com/a/58403262 for more information.
The text was updated successfully, but these errors were encountered: