You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently this workflow expects to have the Task Definition Json to be part of the GitHub Repo.
If this action can be enhanced to fetch the task definition just by using family:revision provided to AWS.ECS. describeTaskDefinition API and then rendering it further , Then Users do not need to check in the task definition Json in the Repo.
Optionally - Updated task definition can be registered back using registerTaskDefinition API call with updated ECR Image ID.
This will achieve -
Better user confidence to avoid checking in Spec file containing references to various AWS ARNs (Account Id ) etc.
It will be guaranteed that Task Definition will always be correct / no need to validate its format specs etc.
The text was updated successfully, but these errors were encountered:
Good workaround, but the issue with this is that the tags are not pulled into the task definition. And removing the --query 'taskDefinition' and including --include TAGS then means it just fails, as the task def is not in the correct format.
Currently this workflow expects to have the Task Definition Json to be part of the GitHub Repo.
If this action can be enhanced to fetch the task definition just by using family:revision provided to AWS.ECS. describeTaskDefinition API and then rendering it further , Then Users do not need to check in the task definition Json in the Repo.
Optionally - Updated task definition can be registered back using registerTaskDefinition API call with updated ECR Image ID.
This will achieve -
The text was updated successfully, but these errors were encountered: