We think we need to load the flow to generate the OpenAPI schema for its parameters. We could do this at an earlier time and store the schema JSON somewhere?

This issue is stale because it has been open 30 days with no activity. To keep this issue open remove stale label or comment.

This issue is stale because it has been open 30 days with no activity. To keep this issue open remove stale label or comment.

+1 on this - Using both the previous deployment.apply() and currently prefect deploy require me to have all dependencies installed. This has frustrating implications when I'm running this in any CI/CD fashion as I have to install packages into container, and then install the packages again in the builder to deploy.

+1 on this.
I'm surprised this seems like quite a stale issue. How are others solving for this? We have this problem for deploying flows from a centralised CICD but each flow runs using a different docker image and we don't want the CICD to have ALL the requirements at runtime, nor build docker images for the simple task of creating a deployment config.

+1 on this.

On CI/CD waste a lot of time to install dependencies which already installed on Docker image (for example)

Would love to see this behavior changed. My initial understanding of the prefect.yaml / deployment.yaml file was that all necessary metadata was present, rendering it unnecessary to manipulate the Python representation of the flow. It certainly complicates CI/CD.

My workaround will be to install flows in my CI/CD environment, and to have a separate build action for each flow, but this not ideal from a code hygiene and performance perspective.

Any updates on this issue? Having to install all dependencies to create a simple deployment object is kind of cumbersome and conflicts with the purpose of separating flow's dependencies using different images.

My workaround will be to install flows in my CI/CD environment, and to have a separate build action for each flow, but this not ideal from a code hygiene and performance perspective.

Here too. I use PIpfile with pipenv to ensure all works properly.

Dockerfile (image where run flow)

...
RUN pip install --no-cache-dir pipenv==${PIPENV_RELEASE} && \
    pipenv sync --clear --system                         && \
    pip cache purge

CI/CD (GitHub Actions)

      - name: Setup Python env
        uses: actions/setup-python@v4
        with:
          python-version: ${{ vars.PYTHON_VERSION }}

      - name: Setup Prefect CLI
        run: |
          pip install --no-cache-dir prefect==${{ vars.PREFECT_CLI_VERSION }}

      - name: Setup pipenv and Install dependencies
        working-directory: ${{ env.PREFECT_FLOW_NAME }}
        run: |
          pip install --no-cache-dir pipenv==${{ vars.PIPENV_RELEASE }}
          pipenv sync --clear --system

     ...
     # step to prefect deploy

So, I ensure that CI/CD needs the requirements like Dockerfile where build a flow image.

+1 on this. Currently I deal with that by calling the external packages only inside functions.

+1 on this.

Thank you for all the +1. We'll look more into this.

adding another +1

it is so frustrating issue..

+1