Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting "unexpected key" github CI error while deploying aws ecs #164

Closed
allisaurus opened this issue Jan 26, 2021 · 3 comments
Closed

Getting "unexpected key" github CI error while deploying aws ecs #164

allisaurus opened this issue Jan 26, 2021 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@allisaurus
Copy link
Contributor

Additional fields present in the results of ecs:DescribeTaskDefinition are being validated against, causing failures for users who pipe these results into this action.

First reported here:
https://github.com/aws-actions/amazon-ecs-render-task-definition/issues/38#issuecomment-767667278

We are currently working on a fix which adds these properties to the list of IGNORED_TASK_DEFINITION_ATTRIBUTES

@allisaurus
Copy link
Contributor Author

Fix has been merged, and will be released in the very near future.

Those effected should be able to point their action workflows at aws-actions/amazon-ecs-deploy-task-definition@master to use + test the latest.

@allisaurus
Copy link
Contributor Author

This issue has been addressed in v1.4.2!

Please let us know if you continue to encounter this issue.

@mlecar
Copy link

mlecar commented Feb 13, 2021

Hi @allisaurus , Is there a way to silence these warnings? I am using the file that I registered using aws ecs register-task-definition.

Run aws-actions/amazon-ecs-deploy-task-definition@v1.4.2
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.
Warning: Ignoring property 'registeredAt' 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 'registeredBy' 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants