Dave D
02/28/2024, 4:42 AMprefect deployment schedule set
command?
Its mentioned on line 636 in src/prefect/cli/deployment.py for the _set_schedule function but when running help on that name it says there is no command for that
prefect deployment schedule set --help
Usage: prefect deployment schedule [OPTIONS] COMMAND [ARGS]...
Try 'prefect deployment schedule --help' for help.
╭─ Error ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ No such command 'set'. │
╰───────────────────────────────────Marvin
02/28/2024, 4:43 AMprefect deployment schedule set
command isn't correctly documented or might not exist as you would expect in the current CLI implementation. The search in the Prefect documentation did not return relevant information regarding this specific command.
Moreover, I found some GitHub issues related to Prefect deployments and schedules, but none that directly address the existence or usage of prefect deployment schedule set
. Issues regarding scheduling and deployments typically discuss features or behaviors such as:
- The desire for a flag to prevent deployments from being set to active upon deployment when they should be paused (#11107).
- Requests for a --overwrite=False
flag to avoid overwriting settings in the UI with CLI deployments (#6644).
- Discussions about property inconsistencies when using prefect.Deployment
(#9220).
If the set
subcommand is indeed supposed to exist but is not functioning or documented, it could be a bug or oversight. You may wish to open an issue on the Prefect GitHub repository to clarify this command's status or to report an issue if it is not working as expected.Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.
Powered by