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

Hi Prefect Team - I have a question on using blocks in the prefect.yaml file for deployments.

```prefect-version: 2.10.20
name: analyst-operations-qep-yaml # ex: position-pnl-pipeline-yaml

pull:
    - prefect.deployments.steps.git_clone:
        repository: <https://github.com/***/***-***.git>
        branch: "main"
        credentials: "{{ prefect.blocks.github-credentials.sra-service-account }}"

definitions:
    work_pools:
        ecs_work_pool: &amp;ecs_work_pool
            name: "{{ prefect.blocks.string.ecs-work-pool }}"
            work_queue_name: default
            job_variables:
                image: "*****.<http://dkr.ecr.us-east-2.amazonaws.com/py310-base:0.0.3|dkr.ecr.us-east-2.amazonaws.com/py310-base:0.0.3>" 

        ny4_work_pool: &amp;ny4_work_pool
            name: "{{ prefect.blocks.string.ny4-work-pool }}"
            work_queue_name: default
            job_variables:
                image: "****.<http://dkr.ecr.us-east-2.amazonaws.com/py310-base:0.0.3|dkr.ecr.us-east-2.amazonaws.com/py310-base:0.0.3>" 

deployments:
    - name: Set QEP Status
      description: null # optional
      entrypoint: QEP/setQEPstatus.py:set_qep_status 
      work_pool: *ecs_work_pool
      parameters: {} # optional parameters overrride here
      schedule:
        cron: "1 19 * * *"
        timezone: "America/Chicago"```


This is the error we receive: This deployment configuration references work pool '{{ prefect.blocks.string.ecs-work-pool }}' which does not exist. This means no worker will be able to pick up its runs. You can create a work pool in the Prefect UI.

When we just add the name it works fine, but we want to make it dynamic based on the block in each workspace.

The block value and the work pool name are the same, so I'm not sure why this error is occurring

Thanks for raising this <@U02U61Q47QR>! Looks like blocks aren’t currently resolved in that section of the `deployment.yaml`. I’ll open up an issue and we’ll work on fixing that.