-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
tagsSchema should not set Computed to true #730
Labels
Comments
Merged
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
locked and limited conversation to collaborators
May 4, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When there are no tags for a resource (I've tested it with resource aws_route_table), tags in master (at bb3bbcc) will alway plan changes to modify or add tag
#
with<computed>
, in my tests this just resulted in a tag with key#
and value""
.Debugging shows there are no changes, but
NewComputed
is set to true. An apply sets or keeps the value for tag#
to/at""
. A new planning session takes us back to where we were.Debugging line showing the diff:
Removing
Computed: true
from the schema intags.go
will trigger, AFAICS, correct behaviour:The text was updated successfully, but these errors were encountered: