[Docs]:

[MississippiBrenn]

Documentation Link

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/medialive_channel#input-loss-failover-settings

Description

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/medialive_channel#input-loss-failover-settings

automatic_failover_conditions should be automatic_failover_condition

References

No response

Would you like to implement a fix?

None

[github-actions]

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.

[justinretzolk]

Hey @MississippiBrenn 👋 Thank you for taking the time to raise this! I took a look over the documentation that you linked, and couldn't find an argument of automatic_failover_conditions, however, I did find automatic_input_failover_settings.failover_conditions, which looks like it should instead be automatic_input_failover_settings.failover_condition -- is that what you were looking to report?

[github-actions]

This functionality has been released in v5.31.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!

[github-actions]

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.