containerDefinitions in ECS TaskDefintion should be objects and not a string

[martinflemingdev]

What problem are you facing?

Currently the containerDefinitions array in the ECS TaskDefintion component takes a string representation of a JSON object.
This makes patching specific fields and verification very difficult.
Crossplane-contrib provider uses key:value objects instead.

How could Official AWS Provider help solve your problem?

Please consider adopting the same approach as crossplane-contrib provider and provide Key:Value pairs instead of a string representation of a JSON object.

[jpoley]

This is blocking any use of patching, or real adoption. (can't use this string, and for that the community provider is better), also this is not specific to ecs, but an overall upjet related issue. we'd like a path forward

[github-actions]

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

[github-actions]

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

[github-actions]

This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!