Skip to content

[Bug] Data source for security roles is unusable due to 'Invalid address to set: []string{"description"}' #880

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

Closed
sym-stiller opened this issue Oct 28, 2024 · 1 comment · Fixed by #884
Labels
bug Something isn't working

Comments

@sym-stiller
Copy link

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:

  1. Have at least one elasticstack_elasticsearch_security_role data source in your TF plan with a provider version >= 0.11.9
  2. 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
Image
Image
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
@sym-stiller sym-stiller added the bug Something isn't working label Oct 28, 2024
@sym-stiller 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
@tobio
Copy link
Member

tobio commented Oct 29, 2024

Thanks @sym-stiller, this will be fixed in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants