Expose Snowflake Integration Manager through Snowflake Connector block

[robfreedy]

Describe the current behavior

Currently, the SnowflakeCredentials block exposes the private key directly, which creates potential security risks. Users who need to work with Snowflake Integration Manager must retrieve the private key from the credentials block, which unnecessarily exposes sensitive information that could be exfiltrated.

Describe the proposed behavior

Expose the Snowflake SimpleIngestManager directly through the SnowflakeConnector instead of requiring users to extract the private key from the credentials block. This would:

1. Keep credentials properly encapsulated within the connector
2. Provide a more secure workflow that prevents secret exfiltration
3. Create a more cohesive experience for Snowflake-related operations

Example Use

See github link attached above

Additional context

No response

[zzstoatzz]

hi @robfreedy - thanks for the issue. I am wondering if you can expand on this

the SnowflakeCredentials block exposes the private key directly, which creates potential security risks

which part is insecure and why?

the linked repository is not a dependency of prefect-snowflake at this time but it could be if there was some demonstrable value!