[cf3901646]

Problem

dstack apply -f /abs/path/.dstack.yml crashes with a traceback before contacting the server:

ValueError: '/tmp/a/.dstack.yml' is not in the subpath of '/Users/me'

load_apply_configuration() always converted the configuration path into a path relative to the current directory:

return str(configuration_path.absolute().relative_to(Path.cwd())), conf

Path.relative_to() raises ValueError for any file outside the cwd, so applying a configuration by absolute path — or from any other directory — never got past argument parsing. Relative paths containing .. happened to work because Path.absolute() keeps the .. segments.

Fixes #4444.

Fix

Try the relative form first (unchanged behavior for configurations under the cwd) and fall back to the absolute path when the configuration is not under the cwd. Relative repos and files entries are resolved against the configuration's directory (Path(configuration_path).resolve().parent), so they keep resolving correctly either way. The stdin (-f -) path is untouched.

Tests

New src/tests/_internal/cli/services/configurators/test_apply_configuration.py:

• a configuration outside the cwd is returned as an absolute path and still parses
• a configuration inside the cwd is still returned as a relative path
• a relative path with .. segments is still returned unchanged
• a missing configuration still raises ConfigurationError

$ uv run pytest src/tests/_internal/cli/services/configurators/test_apply_configuration.py -q
4 passed

The first test fails on main with the reported ValueError and passes with the patch.

uv run ruff check and uv run ruff format --check pass on both changed files.