scaffold-snowflake-connector

Scaffolding a Snowflake connector data source for crowd.dev requires providing the platform name and source name to generate boilerplate files, including buildSourceQuery, transformer, activity types, migrations, and type registrations across multiple touch points with explicit user validation.

Adding a Snowflake connector to crowd.dev requires boilerplate files for buildSourceQuery, transformers, activity types, migrations, type definitions, and integration wiring. The scaffold generates these files across multiple touch points while following existing platform conventions to ensure structural consistency.

No, the Snowflake connector scaffold manages exactly one platform and one source per run. This limitation enforces zero-assumption practices and explicit user validation before writing any file, ensuring structural consistency across the crowd.dev architecture.

Generating Snowflake connector boilerplate requires two explicit inputs: the platform name and the source name. These values drive the scaffolding of type definitions, migrations, integration wiring, and transformer functions while following existing crowd.dev platform conventions.

Code generation ensures consistency for new crowd.dev data sources by following existing platform conventions and producing a uniform code structure for new platform-source combinations. The scaffold applies zero-assumption practices with explicit validation before writing any boilerplate files.