You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.
Hello
We started getting deprecation warnings like this:
for bt gc policies, we got the following error:
Warning: Deprecated Attribute
on bigtable.tf line 34, in resource "google_bigtable_gc_policy" "foo":
34: days = 3
Deprecated in favor of duration
(and 19 more similar warnings elsewhere)
That's fine, so Ok, we change 3d to, say, 72h. At that point, though, terraform apply returns the error Error: doesn't support update if we try to a change like this
We can remove the state and try to reimport it, however, then we find out that this is not an importable resource
Error: resource google_bigtable_gc_policy doesn't support import
It may be safe to simply remove the state, reapply everything, and not worry about dupe resources being left behind, but I don't know enough about bt garbage-collection policies to know if this is safe / sane. In either event, the current experience is frustrating.
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked as resolved and limited conversation to collaborators
Mar 27, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Hello
We started getting deprecation warnings like this:
That's fine, so Ok, we change 3d to, say, 72h. At that point, though, terraform apply returns the error
Error: doesn't support update
if we try to a change like thisWe can remove the state and try to reimport it, however, then we find out that this is not an importable resource
It may be safe to simply remove the state, reapply everything, and not worry about dupe resources being left behind, but I don't know enough about bt garbage-collection policies to know if this is safe / sane. In either event, the current experience is frustrating.
Terraform Version
(tried with 3.57.0 as welll)
Affected Resource(s)
Terraform Configuration Files
Debug Output
can provide if needed
Panic Output
Expected Behavior
When changing from, say, 30d to 720h for
duration
, we'd expect that the change will be a noop or state only changeActual Behavior
Terraform gives the error
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: