https://prefect.io logo
Title
m

Michael Viescas

01/07/2023, 5:10 AM
Hi. We're running @Anna Geller’s dataflow-ops project: https://github.com/anna-geller/dataflow-ops/blob/main/.github/workflows/main.yaml The ecr-ecs-block github actions flow stopped working with a 409 error: "Client error '409 Conflict' for url '***/block_documents/'" It's happening during the "ecs.image=" line.
- name: Prefect ECS block
        run: |
          cat <<EOF > ecs_block.py
          from prefect_aws.ecs import ECSTask
          
          block_ = "$BLOCK"
          ecs = ECSTask.load(block_)
          ecs.image = "${{ steps.build-image.outputs.image }}"
          ecs.save(block_, overwrite=True)
          
          EOF
          python ecs_block.py
Does the ECSTask block still support changing the image after loading it from an existing block? I'm having trouble finding it when looking at the documentation here: https://prefecthq.github.io/prefect-aws/ecs/#prefect_aws.ecs.ECSTask.image Prefect Version: 2.7.7
āœ… 1
Upon further troubleshooting, I suspect this is a problem with the most recent release of Prefect. I can't push deployments anymore either, similar to what Elliot Wilson says in the thread below. I get a 422 error when I try to push blocks or deployments to the prefect API.
Confirming that rollback worked: prefect==2.7.3 prefect-aws==0.2.1
a

Anna Geller

01/08/2023, 3:41 PM
Thanks for reporting this, I will investigate it first time tomorrow
Just saw message from Kalise, can you confirm it works now? Must have been through the issue mentioned in the thread below
m

Michael Viescas

01/08/2023, 4:50 PM
I will revert to 2.7.7 and confirm. Thanks!
2.7.7 is working fine now. Thanks!
:gratitude-thank-you: 1
šŸ‘ 1
a

Anna Geller

01/08/2023, 8:33 PM
thanks so much for confirming that!
šŸ‘ 1