[Data 1419] Update parameter validation in prefect flow deployment #1670
Conversation
There was a problem hiding this comment.
Pull request overview
This pull request updates the Prefect flow deployment configuration to enable parameter schema validation by setting enforce_parameter_schema: true. According to the description, this aligns with Prefect's default behavior where parameter validation is checked by default.
Changes:
- Changed
enforce_parameter_schemafromfalsetotruein the Prefect deployment configuration
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| work_queue_name: "default", | ||
| entrypoint: f.entrypoint, | ||
| enforce_parameter_schema: false, | ||
| enforce_parameter_schema: true, |
There was a problem hiding this comment.
Setting enforce_parameter_schema to true unconditionally may cause issues for flows that don't define a parameter_openapi_schema. When enforce_parameter_schema is true but no schema is provided, Prefect may reject flow runs with parameters. Consider making this conditional based on whether f.parameter_openapi_schema is defined, or ensure all flows in the system have schemas defined.
| enforce_parameter_schema: true, | |
| enforce_parameter_schema: !!f.parameter_openapi_schema, |
The validate parameters is checked by default
