For executions, it is possible to use a custom yaml path by defining either the project or the commit:
vh --project-mode remote --project <project-id> exec run <step-name>vh exec run <step-name> --commit <commit-id>
This does not work for pipelines. Using the project results in the following error:
raise ValueError('RemoteProjects require an explicit commit identifier')
ValueError: RemoteProjects require an explicit commit identifier
Defining the commit results in this error:
FileNotFoundError: [Errno 2] No such file or directory: '/Path/to/project/root/valohai.yaml'
Note that adhoc pipelines work fine with the custom yaml path.
For executions, it is possible to use a custom yaml path by defining either the project or the commit:
vh --project-mode remote --project <project-id> exec run <step-name>vh exec run <step-name> --commit <commit-id>This does not work for pipelines. Using the project results in the following error:
Defining the commit results in this error:
Note that adhoc pipelines work fine with the custom yaml path.