write-script-snowflake

Parameterized Snowflake queries use ? placeholders with preceding comments to declare parameter names and types, preventing SQL injection and improving reusability. This pattern lets you write once and execute safely with different inputs across analytics, reporting, and ETL workflows.

Yes. Windmill integrates parameterized Snowflake scripts through metadata generation and CLI deployment. Create your script with ? placeholders and comments, run `wmill script generate-metadata` to produce .script.yaml and .lock files, then deploy via `wmill sync push`.

Convert recurring queries by replacing hardcoded values with ? placeholders and adding preceding comments that name and type each parameter. This creates a template deployable across multiple workflows, reducing errors and maintenance overhead in data analytics pipelines.

Yes. The Windmill CLI (`wmill`) generates metadata from your parameterized script and deploys it to Windmill flows. The `generate-metadata` command creates configuration files required before pushing scripts via `wmill sync push`.

Parameter metadata documents input names, types, and placeholders in a machine-readable format, enabling Windmill to validate inputs, generate UI forms, and enforce type safety across recurring data queries and ETL jobs.

Without preceding comments declaring parameter names and types, the metadata generation step cannot map placeholders to inputs, breaking integration with Windmill workflows and preventing safe, repeatable parameter passing in your scripts.