Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

I've run into the "too-many-revisions" issue using ECS Task Block in Prefect2. I've removed everything from the Task Definition property and added an explicit Task Definition ARN, but I'm still getting new revisions of the definition. Is there something I'm missing to prevent new revisions?

You can see the diff that causes a new definition to be registered by enabling debug logs

<https://github.com/PrefectHQ/prefect-aws/pull/166>

<@U01CEUST9B5> Thanks for the direction. It looks like "awslogs-stream-prefix":  in logConfiguration is being populated with the randomly generated Flow run name. Is there a way to set a standard prefix?

You can use `cloudwatch_logs_options` to override that value

```if self.configure_cloudwatch_logs:
            container["logConfiguration"] = {
                "logDriver": "awslogs",
                "options": {
                    "awslogs-create-group": "true",
                    "awslogs-group": "prefect",
                    "awslogs-region": region,
                    "awslogs-stream-prefix": self.name or "prefect",
                    **self.cloudwatch_logs_options,
                },
            }```

You could also disable configuration of cloudwatch logs and do it yourself if you want more control

I accidentally saved my ECS Task block with values in 'Task Customizations', deleted the values after a failed run, but am still getting the error: task_customizations
  instance of JsonPatch expected (type=type_error.arbitrary_type; expected_arbitrary_type=JsonPatch)

After futile attempts to correct the issue I decided to just create a new ECS Task and update the Deployment, but even trying to update the deployment gives me the Task Customizations error. Is there a simple fix for this?

I don’t fully understand unfortunately :confused:

Perhaps using `prefect deployment inspect` can you more insight?

It turns out if you save a value in Task Customization then delete the value and save again the task_customizations property gets saved without the empty array []. To fix the ECS Task block I had to put the value of an empty array in Task Customization and save. This looks like a bug in the code, but the work-around is working.

I'm moving back on to the logging setting and will keep you posted.

Cloudwatch Log Options did the trick. Thanks for pointing me in the right direction