Skip to content
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

[Bug]: aws_iot_indexing_configuration does not support named shadows #27532

Closed
karlpokus opened this issue Oct 28, 2022 · 5 comments · Fixed by #26862
Closed

[Bug]: aws_iot_indexing_configuration does not support named shadows #27532

karlpokus opened this issue Oct 28, 2022 · 5 comments · Fixed by #26862
Labels
bug Addresses a defect in current functionality. service/iot Issues and PRs that pertain to the iot service.
Milestone

Comments

@karlpokus
Copy link
Contributor

Terraform Core Version

v1.3.3

AWS Provider Version

v4.37.0

Affected Resource(s)

aws_iot_indexing_configuration

Expected Behavior

Indexing should be configured

Actual Behavior

Indexing was NOT configured. Instead I got an error message that required field "filter" must not be empty. There is no such field in the documentation https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iot_indexing_configuration. It is however in https://docs.aws.amazon.com/iot/latest/developerguide/managing-index.html.

A side note: It seems the "filter" field is missing from the aws cli too.

Relevant Error/Panic Output Snippet

Error: error updating IoT Indexing Configuration: InvalidRequestException: NamedShadowNames Filter must not be empty for enabling NamedShadowIndexingMode

Terraform Configuration Files

resource "aws_iot_indexing_configuration" "example" {
  thing_indexing_configuration {
    thing_indexing_mode              = "REGISTRY_AND_SHADOW"
    thing_connectivity_indexing_mode = "STATUS"
    device_defender_indexing_mode    = "OFF"
    named_shadow_indexing_mode       = "ON" # this is broken
  }
}

Steps to Reproduce

Create the resource above and apply.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

No response

@karlpokus karlpokus added bug Addresses a defect in current functionality. needs-triage Waiting for first response or review from a maintainer. labels Oct 28, 2022
@github-actions
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/iot Issues and PRs that pertain to the iot service. label Oct 28, 2022
@ewbankkit ewbankkit removed the needs-triage Waiting for first response or review from a maintainer. label Oct 28, 2022
@karlpokus
Copy link
Contributor Author

I'd be happy to contribute a fix if I could get some pointers on where to start looking.

@Oltier
Copy link
Contributor

Oltier commented Nov 21, 2022

Give me a thumbs up so that the PR review gets prioritized :) My PR should fix this
#26862

@github-actions
Copy link

This functionality has been released in v5.23.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/iot Issues and PRs that pertain to the iot service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants