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

Unexpected key 'enableFaultInjection' found in params when running action #701

Closed
Sickday opened this issue Jan 6, 2025 · 4 comments
Closed

Comments

@Sickday
Copy link

Sickday commented Jan 6, 2025

Greetings!

This morning our organization started to receive the following message when running the aws-actions/amazon-ecs-deploy-task-definition@v1 action.

Error: Failed to register task definition in ECS: Unexpected key 'enableFaultInjection' found in params
Error: Unexpected key 'enableFaultInjection' found in params

We haven't made any changes to the workflow that runs this action in several months, and it's unclear what may be causing this issue. Please let me know additional information may help in resolving this.

Below is the log from the action run

2025-01-06T16:55:33.5449275Z ##[group]Run aws-actions/amazon-ecs-render-task-definition@v1
2025-01-06T16:55:33.5449657Z with:
2025-01-06T16:55:33.5449872Z   task-definition: task-definition.json
2025-01-06T16:55:33.5450193Z   container-name: <redacted>
2025-01-06T16:55:33.5450692Z   image: <redacted>
2025-01-06T16:55:33.5451173Z   environment-variables: <redacted>

2025-01-06T16:55:33.5451468Z env:
2025-01-06T16:55:33.5451656Z   AWS_DEFAULT_REGION: us-east-1
2025-01-06T16:55:33.5451896Z   AWS_REGION: us-east-1
2025-01-06T16:55:33.5452239Z   AWS_ACCESS_KEY_ID: ***
2025-01-06T16:55:33.5452580Z   AWS_SECRET_ACCESS_KEY: ***
2025-01-06T16:55:33.5457322Z   AWS_SESSION_TOKEN: ***
2025-01-06T16:55:33.5457548Z ##[endgroup]
2025-01-06T16:55:33.6961158Z Task definition file will be used.
2025-01-06T16:55:33.7309245Z ##[group]Run aws-actions/amazon-ecs-deploy-task-definition@v1
2025-01-06T16:55:33.7309646Z with:
2025-01-06T16:55:33.7309997Z   task-definition: /home/runner/work/_temp/task-definition--1677-0iawIJY0eYU0-.json
2025-01-06T16:55:33.7310428Z   service: <redacted>
2025-01-06T16:55:33.7310712Z    cluster: <redacted>-cluster
2025-01-06T16:55:33.7310961Z    wait-for-service-stability: true
2025-01-06T16:55:33.7311206Z env:
2025-01-06T16:55:33.7311393Z   AWS_DEFAULT_REGION: us-east-1
2025-01-06T16:55:33.7311627Z   AWS_REGION: us-east-1
2025-01-06T16:55:33.7311943Z   AWS_ACCESS_KEY_ID: ***
2025-01-06T16:55:33.7312268Z   AWS_SECRET_ACCESS_KEY: ***
2025-01-06T16:55:33.7317017Z   AWS_SESSION_TOKEN: ***
2025-01-06T16:55:33.7317248Z ##[endgroup]
2025-01-06T16:55:33.9995954Z ##[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.
2025-01-06T16:55:34.0004215Z ##[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.
2025-01-06T16:55:34.0011723Z ##[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.
2025-01-06T16:55:34.0018867Z ##[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.
2025-01-06T16:55:34.0025975Z ##[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.
2025-01-06T16:55:34.0032786Z ##[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.
2025-01-06T16:55:34.0039354Z ##[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.
2025-01-06T16:55:34.0061876Z ##[error]Failed to register task definition in ECS: Unexpected key 'enableFaultInjection' found in params
2025-01-06T16:55:34.0070240Z ##[error]Unexpected key 'enableFaultInjection' found in params
2025-01-06T16:55:34.0081274Z (node:1688) NOTE: The AWS SDK for JavaScript (v2) will enter maintenance mode
2025-01-06T16:55:34.0083069Z on September 8, 2024 and reach end-of-support on September 8, 2025.
2025-01-06T16:55:34.0084432Z 
2025-01-06T16:55:34.0085094Z Please migrate your code to use AWS SDK for JavaScript (v3).
2025-01-06T16:55:34.0086928Z For more information, check blog post at https://a.co/cUPnyil
2025-01-06T16:55:34.0088899Z (Use `node --trace-warnings ...` to show where the warning was created)
2025-01-06T16:55:34.0222131Z Post job cleanup.
2025-01-06T16:55:34.0577532Z Cleaning up orphan processes

Thanks,

Patrick W.

@lmancilla
Copy link

Just migrate to @v2 ;)

@jesperborgstrup
Copy link

Upgrading to @v2 solved the issue for me, requiring no other changes in my setup 👍

@omkhegde
Copy link
Contributor

omkhegde commented Jan 6, 2025

Hello @Sickday thank you for submitting this issue. As other users have pointed out, please migrate to v2 of the action to be able to use the enableFaultInjection property which was added after the release of v2 of our action.

Closing the issue, but please feel free to reopen if you have further questions. Thank you.

@omkhegde omkhegde closed this as completed Jan 6, 2025
@bellti9er
Copy link

Thanks bros !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants