BUG: RegisterTaskDefinition operation no longer accepts task-definitions without an `image`

When following the instructions for using this action here: https://aws.amazon.com/blogs/opensource/github-actions-aws-fargate/

…I can no longer register the task definition because the image is filled in during the GitHub workflow after the image is built.

This must have changed recently because I implemented this workflow for a different project as recently as November.

task-definition.json

{
  "family": "web-task-staging",
  "networkMode": "awsvpc",
  "containerDefinitions": [
    {
      "name": "web-container-staging",
      "memory": 200,
      "cpu": 10,
      "essential": true,
      "portMappings": [
        {
          "containerPort": 80,
          "hostPort": 80
        }
      ],
      ...

And the error: An error occurred (ClientException) when calling the RegisterTaskDefinition operation: Container.image should not be null or empty.

[paragbhingre]

@thomasmost great to know that both the projects are working fine. I closing this issue for now, if you have any more concerns then please feel free to reopen this issue.

P.S. In order to avoid getting the error mentioned in the issue above, we need to mention the image tag in task def JSON with the string filled in (could be anything, could be “TBD”).

[thomasmost]

Correct, neither project is specifying an image tag and both are now working