@Marvin Hello! Im running into a problem with my prefect deployment, it has been working fine but I just updated the base image and now it is having issues with root/current directory pathing. Here is the issue that I am running into: This is the deployment logic in prefect.yaml for pulling the source code and setting up some infra - this has worked previously but now I am getting an error where it says it can not find a module called

base-prefect

.

pull:
- prefect.deployments.steps.git_clone: &clone_repo
    repository: my_repo
    branch: test-deploy-branch
    access_token: token_in_secrets

definitions:
  actions:
    pull_and_setup: &pull_and_setup
    - prefect.deployments.steps.git_clone:
        <<: *clone_repo
    - base-prefect.utilities.secrets.retrieve_secrets.service_secrets:  <-- this is throwing errors
        id: retrieve_secrets

Here is the flow deployment

- name: my flow
  version:
  tags: []
  description: 
  entrypoint: flows/my_flow.py:my_flow
  parameters
  work_pool:
    name: kubernetes-work-pool
    work_queue_name:
    job_variables:
      image: us-docker.pkg.dev/project/prefect/base_image:latest
  schedule:
  pull: *pull_and_setup

With the older image I have this works fine - but when I build and push up a new image I get that error. So Im wondering if maybe something changed with the

prefecthq/prefect:2-python3.11

base image? on the old image if I print out the current working dir I get

/opt/prefect/base-prefect

but with the new image I get

/opt/prefect/base-prefect-test-deploy-branch

- so Im not sure why it is appending my branch name to this and I am wondering if this is causing the problems. Thank you for any help I can get on this!