Pavel Shiriaev
07/27/2023, 12:48 PMValidation of flow parameters failed with error:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/prefect/engine.py", line 304, in retrieve_flow_then_begin_flow_run
parameters = flow.validate_parameters(flow_run.parameters)
File "/usr/local/lib/python3.10/site-packages/prefect/flows.py", line 344, in validate_parameters
args, kwargs = parameters_to_args_kwargs(self.fn, parameters)
File "/usr/local/lib/python3.10/site-packages/prefect/utilities/callables.py", line 158, in parameters_to_args_kwargs
raise SignatureMismatchError.from_bad_params(
prefect.exceptions.SignatureMismatchError: Function expects parameters ['minio_secret_path', 'bucket_name', 'bucket_upload_path', 'dwh_secret_path', 'db_name', 'collection', 'pg_schema', 'target_table', 'postgres_name', 'default_schema', 'username', 'password', 'url', 'port', 'sections_dict', 'dwh_rule', 'api_post'] but was provided with parameters ['minio_secret_path', 'minio_host', 'minio_port', 'bucket_name', 'bucket_upload_path', 'dwh_secret_path', 'db_ip', 'dp_port', 'db_name', 'collection', 'dwh_rule', 'api_post']
First run was ok. But after several hours passed, crontab started new flow all mentioned parameters disappeared some how. What is wrong? I do not use these parameters: 'pg_schema'
, 'target_table'
, 'postgres_name'
, 'default_schema'
, 'username'
, 'password'
, 'url'
, 'port'
, 'sections_dict'
in my deploy and flow. Prefect itself decided to add them to the list of required parameters. Why could this happen?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