snowflake-synthetic

Skill: Snowflake Synthetic Test Setup

Use this skill whenever you need to create, update, or verify synthetic test data pipelines in Snowflake for validating DSOA telemetry and dashboards.

Environment Reference (test-qa)

Validated on: test-qa (YOUR_SNOWFLAKE_TEST_ACCOUNT, AWS_US_EAST_1)

Item	Value
CLI connection	snow_agent_test-qa
Snowflake account	YOUR_SNOWFLAKE_TEST_ACCOUNT
Region	AWS_US_EAST_1
DSOA database	DTAGENT_QA_DB
Owner role	DTAGENT_QA_OWNER
Viewer role	DTAGENT_QA_VIEWER
Default warehouse	DTAGENT_WH
Synthetic warehouse	DSOA_TEST_WH (XSMALL, created by setup scripts)
Synthetic database	DSOA_TEST_DB (created by setup scripts)

Note: The connection's default role (YOUR_SNOWFLAKE_TEST_ROLE) cannot see DTAGENT databases. Always use USE ROLE DTAGENT_QA_OWNER explicitly when checking for agent objects.

Design Principle: DSOA-Independence

Synthetic setup scripts must be fully independent of DSOA. They create test data that DSOA will eventually observe, but they must not assume DSOA is already deployed — the whole point is that the environment can be set up before DSOA is deployed for the first time.

Concretely:

• Never reference DTAGENT_* roles, databases, or objects in a setup script. Those objects may not exist yet.
• Do not grant to DTAGENT_QA_VIEWER in the setup script. DSOA's own deploy (--scope=admin,config) handles grants to its viewer role as part of installation.
• Run everything as SYSADMIN (for object creation) and ACCOUNTADMIN (for account-level grants only, e.g. EXECUTE TASK). All created objects are owned by SYSADMIN or transferred to it — no DSOA-specific roles needed.

The DSOA viewer role gains access to DSOA_TEST_DB automatically when DSOA is deployed (its admin SQL grants USAGE on all databases the agent needs to read). No manual grants to DTAGENT_* roles are needed in the setup script.