Action failing with error "Unexpected key 'runtimePlatform' found in params"
See original GitHub issueIt looks like the task definition json returned describe-task-definition
now contains the runtimePlatform
attribute. This is causing builds to break in workflows that fetch the task definition and then mutate them, rather than keep them under version control.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:17
- Comments:5
Top Results From Across the Web
Failed to register task definition in ECS with GitHub Actions
Issue found, I had not correctly updated the task definition json to declare the correct ARN.
Read more >RegisterTaskDefinition - Amazon Elastic Container Service
Registers a new task definition from the supplied family and containerDefinitions . Optionally, you can add data volumes to your containers with the...
Read more >Task definition parameters - Amazon Elastic Container Service
If your cluster doesn't have any registered container instances with the requested CPU units available, the task fails. Supported values for tasks that...
Read more >Task definition - Unknown parameter in input: "
aws ecs register-task-definition --cli-input-json file://td_gravinton.json. Parameter validation failed: Unknown parameter in input: "runtimePlatform", ...
Read more >z/OS Connect EE build toolkit messages - IBM
Explanation, The build toolkit failed to load the configuration properties from the specified file. Action, Check the reason for the failure and correct...
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
I had the same issue and I solved by using the “latest” version of the deploy task definition job.
uses: aws-actions/amazon-ecs-deploy-task-definition@v1
Same, I did the following workaround (probably not recommended, but it works for now as a hot fix):