DEVREL-2147 update snowflake on SDS page#1118
Conversation
|
|
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| # Secure Data Share | ||
|
|
||
| Secure Data Share (SDS) makes your SailPoint identity data available directly in your own [AWS Snowflake](https://aws.amazon.com/financial-services/partner-solutions/snowflake/) account. The provided dataset comprises structured tables that include identity, audit event, entitlement, role, access profile, account, and application data. Secure Data Share is an alternative to SailPoint's [Search](https://documentation.sailpoint.com/saas/help/search/index.html). SDS uses SQL as the query language, whereas Search uses the [Elasticsearch Query Language](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl.html). SQL provides certain advantages over Elasticsearch: joining and aggregating data is easier in SQL, and the Snowflake interface has a built-in SQL explorer and allows you to download your search results in CSV format. SDS also allows you to connect your SailPoint data to your favorite data analytics tools, like [PowerBI](https://learn.microsoft.com/en-us/power-bi/connect-data/service-connect-snowflake) and [Tableau](https://help.tableau.com/current/pro/desktop/en-us/examples_snowflake.htm), further enhancing the reporting capabilities for your SailPoint data. | ||
| Secure Data Share (SDS) makes your SailPoint identity data available directly in your own AWS, Azure, or Google Cloud Platform Snowflake account. The provided dataset comprises structured tables that include identity, audit event, entitlement, role, access profile, account, and application data. Secure Data Share is an alternative to SailPoint's [Search](https://documentation.sailpoint.com/saas/help/search/index.html). SDS uses SQL as the query language, whereas Search uses the [Elasticsearch Query Language](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl.html). SQL provides certain advantages over Elasticsearch: joining and aggregating data is easier in SQL, and the Snowflake interface has a built-in SQL explorer and allows you to download your search results in CSV format. SDS also allows you to connect your SailPoint data to your favorite data analytics tools, like [PowerBI](https://learn.microsoft.com/en-us/power-bi/connect-data/service-connect-snowflake) and [Tableau](https://help.tableau.com/current/pro/desktop/en-us/examples_snowflake.htm), further enhancing the reporting capabilities for your SailPoint data. |
There was a problem hiding this comment.
🔴 The intro (line 19) was updated to say SDS supports an 'AWS, Azure, or Google Cloud Platform Snowflake account', but the Requirements section (line 28) still reads 'You must also have an AWS Snowflake account so that SailPoint can synchronize your tenant data with your Snowflake instance.' This contradicts the broadened messaging this PR is meant to introduce — please update the Requirements sentence to match (e.g., 'You must also have a Snowflake account on AWS, Azure, or GCP').
Extended reasoning...
Bug
This PR partially updates the page to broaden Snowflake cloud-provider support from AWS-only to AWS/Azure/GCP, but only the opening paragraph (line 19) is changed. The Requirements section a few lines down (line 28) still states the AWS-only requirement, creating an internal contradiction on the same short page.
Code Path
- Line 19 (changed by this PR):
Secure Data Share (SDS) makes your SailPoint identity data available directly in your own AWS, Azure, or Google Cloud Platform Snowflake account.
- Line 28 (unchanged by this PR):
You must also have an AWS Snowflake account so that SailPoint can synchronize your tenant data with your Snowflake instance.
Before this PR, both sentences agreed (both said AWS). The PR introduces the contradiction by updating only one of them.
Why Existing Code Doesn't Prevent This
This is plain Markdown documentation — there is no compile-time check that would catch cross-paragraph inconsistencies. A human review (or this comment) is the only safeguard.
Impact
A customer reading the page top-to-bottom will first be told SDS supports three cloud providers, then immediately told in Requirements that an AWS Snowflake account is required. That directly undermines the stated purpose of DEVREL-2147 (broaden the Snowflake cloud-platform messaging) and may steer Azure/GCP customers away from a product they actually qualify for.
Suggested Fix
Update line 28, for example:
-You must also have an AWS Snowflake account so that SailPoint can synchronize your tenant data with your Snowflake instance.
+You must also have a Snowflake account on AWS, Azure, or Google Cloud Platform so that SailPoint can synchronize your tenant data with your Snowflake instance.Step-by-Step Proof
- Open
docs/reporting/secure-data-share/index.mdafter this PR is applied. - Read line 19: it advertises support for AWS, Azure, or GCP Snowflake accounts.
- Scroll to the
## Requirementsheading and read line 28: it states a customer must have an AWS Snowflake account. - The reader now has two mutually-exclusive statements about supported cloud platforms in the same document, with no qualifier reconciling them. That is the bug.
2 participants
Ticket: https://sailpoint.atlassian.net/browse/DEVREL-2147