Eventual Task Definition consistency

[nickdarnell]

I've been personally suffering from

aws_ecs_task_definition.somesystem_task: Creating...
╷
│ Error: reading ECS Task Definition (arn:aws:ecs:REGION:ACCOUNT_ID:task-definition/somesystem_task:20): couldn't find resource

The task definition in question is being updated, but the system is immediately attempting to read it and failing. I poked around and saw how it was being solved with other systems.

It'd be nice if newly created resources were implicitly retried in any context where they're queried vs this specific error handling in each case.

I still need to run acceptance testing and such, this is more of a rough draft of 'bug report by way of PR'

But to reiterate,

it finds the existing task, updates it, but then immediately cant find the brand new revision which definitely exists now (or will soon) in aws fashion.

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[github-actions]

⚠️ Our automation has detected the following potential issues with your pull request

---

❌ Changelog Entry Required (Click to expand)

The proposed change requires a changelog entry. Please see the Changelog Process section of the contributing guide for information on the changelog generation process.

Tip: This check is not triggered for draft pull requests, since the pull request number is not known until the pull request is opened and is required to create a changelog entry. Opening a pull request first as a draft, adding the requisite changelog entry file, and then marking the pull request as ready for review will prevent future warnings.