Changes

Removed deprecated path fallback mechanism for jobs and pipelines

Effectively, it removes an old deprecated behaviour and only relies on the new one introduced here #1273

What's changing?

Assuming there are the following 2 bundle configuration files in your bundle

• ./resources/my_job.yml - this is where the job is defined
• ./override.yml - this is where the notebook path of the job task is overridden

./resources/my_job.yml

resources:
  jobs:
    my_job:
      name: "my job"
      tasks:
        - task_key: notebook_example
          job_cluster_key: default
          notebook_task:
            # if not overridden, this resolves to ./resources/original_notebook.py
            notebook_path: ./original_notebook.py

./override.yml

targets:
  development:
    resources:
      jobs:
        my_job:
          tasks:
            - task_key: notebook_example
              notebook_task:
                # before this PR: this resolves to <BUNDLE_ROOT>/../src/notebook.py first and if that cannot be done, resolves to <BUNDLE_ROOT>/src/notebook.py
                # with this PR: this resolves only to <BUNDLE_ROOT>/../src/notebook.py
                notebook_path: ../src/notebook.py

Before this change, on bundle validate / deploy the notebook_path for notebook_example would resolve to ./src/notebook.py relative to the bundle root because the relative path was relative to where the job is defined (/resources/my_job.yml)

After this change, the notebook_path for notebook_example would resolve to ../src/notebook.py relative to the bundle root because now the path is calculated relative to where it's defined (./override.yml)

Action items

If you are affected by this change, you can do one of the following:

1. (recommended) Make necessary configuration changes to have relative paths defined relative to configuration files they are in, or
2. Pin the CLI version which you use to 0.261.0 or earlier

Tests

Covered by existing acceptance tests