https://prefect.io logo
Join Slack
Powered by
<@ULVA73B9P> How to set no schedule property in de...
# ask-marvin
l
@Marvin How to set no schedule property in deployment without having the Prefect cli asking if I need to schedule the deployment ?
Copy code
# the deployments section allows you to provide configuration for deploying flows
deployments:
- name: sync_tmdb
  version: 1.0.0
  tags:
  - tmdb
  description: Sync TMDB data
  schedules:
  - cron: 0 12 * * *
    timezone: Europe/Paris
    day_or: true
    active: true
    catchup: false
  entrypoint: sync_tmdb/sync_tmdb.py:sync_tmdb
  parameters: {}
  work_pool:
    name: kube
    job_variables:
      <<: *job_variables
      memory_request: "6Gi"
      cpu_request: "2"
      memory_limit: "8Gi"
      cpu_limit: "4"
    work_queue_name:
  concurrency_limit:
  enforce_parameter_schema: true

- name: sync_typesense
  version: 1.0.0
  tags:
  - typesense
  description: Sync all Typesense collections (movies, tv_series, persons, playlists, users)
  entrypoint: sync_typesense/sync_typesense.py:sync_typesense
  parameters: {}
  work_pool:
    name: kube
    job_variables:
      <<: *job_variables
      memory_request: "4Gi"
      cpu_request: "2"
      memory_limit: "6Gi"
      cpu_limit: "4"
  work_queue_name:
  concurrency_limit:
  enforce_parameter_schema: true
Prefect Cli still asking :
Copy code
prefect deploy --all

Deploying sync_typesense
Would you like to configure schedules for this deployment? [y/n] (y):
m
✅ thought for 195.3 seconds
In Prefect 3.x, that prompt appears only when a deployment has no 
schedules
key and the CLI is in interactive mode. You’ve got two good ways to suppress it: 1) Be explicit in prefect.yaml Add 
schedules: []
to deployments that should have no schedules. For your second deployment:
Copy code
- name: sync_typesense
  version: 1.0.0
  tags:
  - typesense
  description: Sync all Typesense collections (movies, tv_series, persons, playlists, users)
  entrypoint: sync_typesense/sync_typesense.py:sync_typesense
  parameters: {}
  work_pool:
    name: kube
    job_variables:
      <<: *job_variables
      memory_request: "4Gi"
      cpu_request: "2"
      memory_limit: "6Gi"
      cpu_limit: "4"
  work_queue_name:
  concurrency_limit:
  enforce_parameter_schema: true
  schedules: []   # add this line
When the 
schedules
key is present (even as an empty list), the deploy command won’t prompt. 2) Disable prompts for the CLI run - One-off:
Copy code
prefect --no-prompt deploy --all
- Or via env var:
Copy code
PREFECT_CLI_PROMPT=false prefect deploy --all
Notes: - There isn’t a `--yes`/`--no` flag specific to `prefect deploy`; use the global 
--no-prompt
flag as shown above. - Your first deployment already has a schedule, so only the ones missing 
schedules
trigger the prompt.
14 Views
Open in Slack
PreviousNext
Powered by