Conversation
DataMasque 3.26.18 stages Snowflake masked data inside Snowflake, so the server no longer exposes the S3 bucket, Azure container, storage integration or Snowflake IAM role fields. Remove them from SnowflakeConnectionConfig. The server detects a Snowflake SPCS deployment from its own environment (is_spcs_env()), so the client no longer states it: snowflake_stage_location and the SnowflakeStageLocation enum are removed. Connections listed from an older server still parse: the removed keys and any snowflake_stage_location value (aws_s3, azure_blob_storage, local, spcs) are dropped on the way in so they are not sent back on create_or_update_connection. Release as 1.4.0; HISTORY.rst calls the breaking change out. BREAKING CHANGE: SnowflakeConnectionConfig loses s3_bucket_name, iam_role_arn, snowflake_azure_container_name, snowflake_azure_connection_string, snowflake_azure_connection_string_encrypted, snowflake_storage_integration_name and snowflake_stage_location; the SnowflakeStageLocation enum is removed from datamasque.client.
carlosfunk
force-pushed
the
DM-3761-snowflake-internal-stage-only
branch
from
September 24, 2026 21:30
e1f9c28 to
44c5417
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
DataMasque 3.26.18 stages Snowflake masked data inside Snowflake, so the server no longer exposes the external staging fields.
SnowflakeConnectionConfiglosess3_bucket_name,iam_role_arn,snowflake_azure_container_name,snowflake_azure_connection_string,snowflake_azure_connection_string_encryptedandsnowflake_storage_integration_name.snowflake_stage_locationand theSnowflakeStageLocationenum are removed as well. The server detects a Snowflake SPCS deployment from its own environment, so the client no longer states it.Connections listed from an older server still parse: the removed keys and any
snowflake_stage_locationvalue (aws_s3,azure_blob_storage,local,spcs) are dropped on the way in and are not sent back oncreate_or_update_connection.Version 1.4.0 with a Breaking HISTORY entry. Requires server 3.26.18.
Testing
pytest518 passed (two SPCS-marker tests removed, one dropped-value case added)ruff check,ruff format --check,mypycleanRelease order
datamasque 3.26.18 (!3769) → this as 1.4.0 → bump the pin in datamasque-automation (1.3.1 still works against 3.26.18 because the server discards the old keys).