feat: Expose GCP_PUBSUB_SERVICE_ACCOUNT attribute in notification integration #871
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.
This updates the "notification integration" resource to expose the GCP_PUBSUB_SERVICE_ACCOUNT generated when using GCP_PUBSUB provider as described in https://docs.snowflake.com/en/user-guide/data-load-snowpipe-auto-gcs.html#step-2-grant-snowflake-access-to-the-pub-sub-subscription.
The field is exposed as "gcp_pubsub_service_account".
Test Plan
This hasn't been tested yet using the acceptance framework.