-
Notifications
You must be signed in to change notification settings - Fork 55
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
docs: update host set plugin filters examples #420
Conversation
This change is to update the example docs for `host_set_plugin` filters attribute to use a list strings instead of just strings. AWS host set plugin expects filters attributes to be passed as a list of strings instead of strings. It is currently backwards compatible with strings due to the migration [normalizeData func](https://github.com/hashicorp/boundary-plugin-aws/blob/7bf9fe2ecf1f20d7ff8aea8306909abcde1d17a4/plugin/service/host/plugin.go#L256) on AWS host plugin. Previously this was not working but [Boundary PR-3338](hashicorp/boundary#3338) fixed the bug.
"filters" = "tag-key=foo", | ||
"filters" = "tag-key=bar" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh, would this example ever have worked? wouldn't jsonencode just set the "filters" key to whatever is defined last?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I don't think it's a valid example. It'd have always just used the last "filters" key
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
This change is to update the example docs for `host_set_plugin` filters attribute to use a list strings instead of just strings. WIthout using a list of strings, Terraform will falsely detect diffs with host set plugin `filters`. AWS host set plugin expects filters attributes to be passed as a list of strings instead of strings. It is currently backwards compatible with strings due to the migration [normalizeData func](https://github.com/hashicorp/boundary-plugin-aws/blob/7bf9fe2ecf1f20d7ff8aea8306909abcde1d17a4/plugin/service/host/plugin.go#L256) on AWS host plugin. Previously this was not working but [Boundary PR-3338](hashicorp/boundary#3338) fixed the bug.
This change is to update the example docs for `host_set_plugin` filters attribute to use a list strings instead of just strings. WIthout using a list of strings, Terraform will falsely detect diffs with host set plugin `filters`. AWS host set plugin expects filters attributes to be passed as a list of strings instead of strings. It is currently backwards compatible with strings due to the migration [normalizeData func](https://github.com/hashicorp/boundary-plugin-aws/blob/7bf9fe2ecf1f20d7ff8aea8306909abcde1d17a4/plugin/service/host/plugin.go#L256) on AWS host plugin. Previously this was not working but [Boundary PR-3338](hashicorp/boundary#3338) fixed the bug.
This change is to update the example docs for
host_set_plugin
filters attribute to use a list strings instead of just strings.WIthout using a list of strings, Terraform will falsely detect diffs with host set plugin
filters
.AWS host set plugin expects filters attributes to be passed as a list of strings instead of strings. It is currently backwards compatible with strings due to the migration normalizeData func on AWS host plugin.
Previously this was not working onCreate but Boundary PR-3338 fixed the bug.