[warning ] Ignoring property 'compatibilities', 'taskDefinitionArn', 'requiresAttributes', 'revision', 'status' in the task definition file
See original GitHub issueJust noticed the following warnings started coming back (worked before)
Deploy new ECS task definition
Deployment started. Watch this deployment's progress in the Amazon ECS console: https://console.aws.amazon.com/ecs/home?region=***#/clusters/stage/services/stage-web/events
Run aws-actions/amazon-ecs-deploy-task-definition@v1
##[warning]Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
##[warning]Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
##[warning]Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
##[warning]Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
##[warning]Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deployment started. Watch this deployment's progress in the Amazon ECS console: https://console.aws.amazon.com/ecs/home?region=***#/clusters/stage/services/stage-web/events
Here is the relevant config is the Github action .yaml
:
- name: Download current ECS task definition
run: aws ecs describe-task-definition --task-definition stage-web --query taskDefinition > task-definition.json
- name: Render new ECS task definition
id: render-task-definition
uses: aws-actions/amazon-ecs-render-task-definition@v1
with:
task-definition: task-definition.json
container-name: stage-web
image: ${{ env.GA_DOCKER_IMAGE }}
Issue Analytics
- State:
- Created 3 years ago
- Reactions:12
- Comments:22 (5 by maintainers)
Top Results From Across the Web
[warning ] Ignoring property 'compatibilities', 'taskDefinitionArn ...
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in...
Read more >describe-task-definition - AWS Documentation - Amazon.com
Describes a task definition. You can specify a family and revision to find information about a specific task definition, or you can simply...
Read more >Enable X-Ray for Crystal :: Amazon App Mesh Workshop
Register a new task definition to add the x-ray container, and enable tracing for the Envoy container. # Define variables # TASK_DEF_ARN=$(aws ecs ......
Read more >aws_ecs_task_definition | Resources | hashicorp/aws
Manages a revision of an ECS task definition to be used in aws_ecs_service . ... "service" container_definitions = file("task-definitions/service.json") ...
Read more >How to reuse declared shell variable in Jenkins pipeline
This should work. Take a look at the following working pipeline. pipeline { agent any stages { stage('Example') { steps { script {...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Not sure if still bugging people, but here’s my approach:
@siddhant-mohan @a-ruban-craftsoft it looks like the failure is actually coming from the amazon-ecs-deploy-task-definition action, which is failing on the presence of the new fields.
We are actively working on a fix and will post updates here: https://github.com/aws-actions/amazon-ecs-deploy-task-definition/issues/164