-
Notifications
You must be signed in to change notification settings - Fork 14
Open
Description
Right now, when you execute with a workflow name:
openfn my-workflow
We run through the Workspace defined in openfn.yaml, and auto-load collections and credentials.yaml.
This is issue is to extend this logic:
- Walk up through parent dirs until we find a workflow.yaml, so that I can run a workflow from inside a workspace. Maybe for example I want to cd into
./workflows/my-workflowand run from there (for easier pathing to supporting state files, for example). We should be able to automatically load the parent workspace in this case. - Whenever we're running inside a workspace folder -that is, if we find an openfn.yaml in the directory structure - go ahead and autoload all settings from it
- Passing
--no-workspaceshould disable this autoload behaviour and stop the CLI finding the openfn.yaml wrapper
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
DevX Backlog