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
Describe the bug
The data source elasticstack_elasticsearch_security_role seems to be unusable since provider version 0.11.9. Each plan will fail with the following message when one such data source is present: Error: Invalid address to set: []string{"description"}
It looks like this error is related to #824 , which introduced the description field to the security_role resource, but not to its data source.
To Reproduce
Steps to reproduce the behavior:
Have at least one elasticstack_elasticsearch_security_role data source in your TF plan with a provider version >= 0.11.9
When running the plan, you should get the error message
Expected behavior
I would have expected the data source to behave like it did before version 0.11.9.
Screenshots
The error message does not change regardless of the role name in use.
Versions:
OS: MacOS Sonoma 14.5
Terraform Version: 1.9.1
Provider version: coming from 0.11.8, trying to upgrade to 0.11.11
Elasticsearch Version: 8.15.2
The text was updated successfully, but these errors were encountered:
sym-stiller
changed the title
[Bug]
[Bug] Data source for security roles is unusable due to 'Invalid address to set: []string{"description"}'
Oct 28, 2024
Describe the bug
The data source
elasticstack_elasticsearch_security_role
seems to be unusable since provider version 0.11.9. Each plan will fail with the following message when one such data source is present:Error: Invalid address to set: []string{"description"}
It looks like this error is related to #824 , which introduced the description field to the security_role resource, but not to its data source.
To Reproduce
Steps to reproduce the behavior:
elasticstack_elasticsearch_security_role
data source in your TF plan with a provider version >= 0.11.9Expected behavior
I would have expected the data source to behave like it did before version 0.11.9.
Screenshots


The error message does not change regardless of the role name in use.
Versions:
The text was updated successfully, but these errors were encountered: