https://prefect.io logo
Join Slack
Powered by
Hey all - I'm running into an issue with deploying...
# ask-community
z
Hey all - I'm running into an issue with deploying my flows when I've already set a schedule in the Prefect Cloud UI I verified this was the issue by removing a schedule in the UI from one of my previously not-deploying flows, and it started deploying successfully. It appears to be some kind of pydantic validation error Are schedules now required to be a part of your deployment code, even if your schedule is specified in in the Prefect Cloud UI? If so, it would be really nice to have schedules working in the Cloud UI as it's a pain to re-deploy just to change schedules Example/error included in thread
Example code (used in github actions): 
prefect deployment build containers/prefect/src/flows/flow_airbyte_2.py:customized_parent_flow -n flow-airbyte -q ${{ steps.<http://set_variables.outputs.DEV|set_variables.outputs.DEV>_STAGE }}-airbyte -t ${{ steps.<http://set_variables.outputs.DEV|set_variables.outputs.DEV>_STAGE }} -t daily -sb github-repository/${{ steps.<http://set_variables.outputs.DEV|set_variables.outputs.DEV>_STAGE }}-data-warehouse-pipeline --param job_name=sql_server_and_salesforce --param run_frequency=daily --param dask_processes=False --param dask_n_workers=1 --param dask_threads_per_worker=8 --param is_full_reset_of_incremental_tables=False --skip-upload --apply
returns error at deploy time
Copy code
Found flow 'prd - Airbyte'
695
The parameter value 1 is parsed as a JSON string
696
The parameter value 8 is parsed as a JSON string
697
Traceback (most recent call last):
698
  File "/home/runner/work/data_warehouse_pipeline/data_warehouse_pipeline/.venv/lib/python3.9/site-packages/prefect/cli/_utilities.py", line 41, in wrapper
699
An exception occurred.
700
    return fn(*args, **kwargs)
701
  File "/home/runner/work/data_warehouse_pipeline/data_warehouse_pipeline/.venv/lib/python3.9/site-packages/prefect/utilities/asyncutils.py", line 260, in coroutine_wrapper
702
    return call()
703
  File "/home/runner/work/data_warehouse_pipeline/data_warehouse_pipeline/.venv/lib/python3.9/site-packages/prefect/_internal/concurrency/calls.py", line 245, in __call__
704
    return self.result()
705
  File "/home/runner/work/data_warehouse_pipeline/data_warehouse_pipeline/.venv/lib/python3.9/site-packages/prefect/_internal/concurrency/calls.py", line 173, in result
706
    return self.future.result(timeout=timeout)
707
  File "/opt/hostedtoolcache/Python/3.9.18/x64/lib/python3.9/concurrent/futures/_base.py", line 439, in result
708
    return self.__get_result()
709
  File "/opt/hostedtoolcache/Python/3.9.18/x64/lib/python3.9/concurrent/futures/_base.py", line 391, in __get_result
710
    raise self._exception
711
  File "/home/runner/work/data_warehouse_pipeline/data_warehouse_pipeline/.venv/lib/python3.9/site-packages/prefect/_internal/concurrency/calls.py", line 218, in _run_async
712
    result = await coro
713
  File "/home/runner/work/data_warehouse_pipeline/data_warehouse_pipeline/.venv/lib/python3.9/site-packages/prefect/cli/deployment.py", line 1138, in build
714
    deployment = await Deployment.build_from_flow(
715
  File "/home/runner/work/data_warehouse_pipeline/data_warehouse_pipeline/.venv/lib/python3.9/site-packages/prefect/deployments.py", line 757, in build_from_flow
716
    await deployment.load()
717
  File "/home/runner/work/data_warehouse_pipeline/data_warehouse_pipeline/.venv/lib/python3.9/site-packages/prefect/deployments.py", line 538, in load
718
    deployment = await client.read_deployment_by_name(
719
  File "/home/runner/work/data_warehouse_pipeline/data_warehouse_pipeline/.venv/lib/python3.9/site-packages/prefect/client/orchestration.py", line 1506, in read_deployment_by_name
720
    return schemas.responses.DeploymentResponse.parse_obj(response.json())
721
  File "pydantic/main.py", line 526, in pydantic.main.BaseModel.parse_obj
722
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
723
pydantic.error_wrappers.ValidationError: 8 validation errors for DeploymentResponse
724
schedule -> interval
725
  field required (type=value_error.missing)
726
schedule -> timezone
727
  argument of type 'function' is not iterable (type=type_error)
728
schedule -> cron
729
  extra fields not permitted (type=value_error.extra)
730
schedule -> day_or
731
  extra fields not permitted (type=value_error.extra)
723
schedule -> timezone
724
  argument of type 'function' is not iterable (type=type_error)
725
schedule -> rrule
726
  field required (type=value_error.missing)
727
schedule -> cron
728
  extra fields not permitted (type=value_error.extra)
729
schedule -> day_or
730
  extra fields not permitted (type=value_error.extra)
731
n
is it this?
👍 1
z
Yes, I will try the above - thank you so much!
n
👍
11 Views
Open in Slack
PreviousNext
Powered by