Prefect-docker `push_docker_image` unwanted cache hit about prefect HOT 3 CLOSED

Another workaround:

    - prefect_docker.deployments.steps.build_docker_image:
        id: build-image
        requires: prefect-docker==0.6.0
        image_name: "{{ prefect.variables.dp_test_project_image_name }}"
        tag: latest
        dockerfile: Dockerfile # added
        additional_tags:
          - "{{ get-commit-hash.stdout }}"
  docker_push: &docker_push
    - prefect_docker.deployments.steps.push_docker_image:
        requires: prefect-docker==0.6.0
        image_name: "{{ build-image.image_name }}"
        tag: "{{ build-image.tag }}"
        additional_tags: "{{ build-image.additional_tags }}"

With this the params to push_docker_image and build_docker_image are not the same, and they are not hiting eachothers cache it seems

from prefect.

Thanks for the bug report @mch-sb!

The intent of caching those steps is to avoid performing duplicate builds and pushes when deploying multiple flows, so you definitely shouldn't see cache hits between a build and a push on a single deployment. Your idea of including the function name in the cache key computation is great! Would you be up for submitting a PR making that change?

from prefect.

hi @mch-sb - thanks for identifying the issue here! the PRs above should fix this for 3.x and 2.x respectively, and will go out with the next release

from prefect.