Unexpected key 'environmentFiles' : Failed to register task definition in ECS

[gaurav-agarwal27]

Using aws-actions/amazon-ecs-deploy-task-definition@v1
I have added environmentFiles in my containerDefinitions of task-definition.json as:

"environmentFiles": [{
    "type": "s3",
    "value": "arn:aws:s3:::ltl-environments/.stg.env"
}],

Getting the following error:

##[error]Failed to register task definition in ECS: There were 5 validation errors:
* UnexpectedParameter: Unexpected key 'environmentFiles' found in params.containerDefinitions[0]
* UnexpectedParameter: Unexpected key 'environmentFiles' found in params.containerDefinitions[2]
* UnexpectedParameter: Unexpected key 'environmentFiles' found in params.containerDefinitions[3]
* UnexpectedParameter: Unexpected key 'environmentFiles' found in params.containerDefinitions[4]
* UnexpectedParameter: Unexpected key 'environmentFiles' found in params.containerDefinitions[5]```

[piradeepk]

It looks like it might be using an older version of the AWS SDK which does not yet support environmentFiles. Will confirm and provide more details.

[gaurav-agarwal27]

Thanks @pkandasamy91 , also I am not sure if the latest version of AWS SDK supports environmentFiles yet ?

[clareliguori]

Hi @gaurav-agarwal27, that feature is not fully released yet, which is why it isn't yet in the SDK. Please watch this roadmap issue for updates on when it is released:
aws/containers-roadmap#371

[gaurav-agarwal27]

Thanks for the update @clareliguori

[piradeepk]

Hi @gaurav-agarwal27, support for environmentFiles have now been released: https://aws.amazon.com/about-aws/whats-new/2020/05/amazon-elastic-container-service-supports-environment-files-ec2-launch-type/

The AWS-SDK v2.679.0 now supports environmentFiles: https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md

[piradeepk]

@gaurav-agarwal27 the dependencies have been updated, and you should now be able to use environmentFiles. Let me know if you're still running into issues.

[gaurav-agarwal27]

@pkandasamy91 thank you so much for the prompt action. Everything is working fine now 😃
Closing the issue.

[spencer-shake]

I'm currently having this same issue, except with enableFaultInjection, which is getting automatically added to the task-definition by this process.

Edit: upgrading from v1 to v2 for aws-actions/amazon-ecs-deploy-task-definition@v2 solved this for me

[edbentinck]

I'm currently having this same issue, except with enableFaultInjection, which is getting automatically added to the task-definition...

Same here. In my case I solved it by upgrading from v1 to v2: aws-actions/amazon-ecs-deploy-task-definition@v2

[spencer-shake]

I'm currently having this same issue, except with enableFaultInjection, which is getting automatically added to the task-definition...

Same here. In my case I solved it by upgrading from v1 to v2: aws-actions/amazon-ecs-deploy-task-definition@v2

Just came back here to say the same thing. Bumping to v2 worked for me as well

[Ahmad-anility]

We are on v2. We have been on v2 for a long time but suddenly started to get this error

[ereid7]

@piradeepk This issue should be reopened. We started experiencing the error mentioned in #64 (comment) with no changes on our end. Upgrading to aws-actions/amazon-ecs-deploy-task-definition@v2 fixed the issue.