atlan-sql-connector-patterns
Atlan SQL Connector Patterns
Choose the right connector strategy and implement it consistently.
Workflow
- Use
references/decision-tree.mdto choosepostgres-minimalorredshift-custom. - Implement required components for selected path.
- Verify auth, preflight, workflow map, and transformation behavior against references.
- Run
atlan-fact-verification-gateif requirements imply source-specific behavior or SDK override risk. - Hand off to
atlan-e2e-contract-validatorfor contract generation.
Rules
- Default to minimal path unless requirements justify custom path.
- For custom path, explicitly document why SDK defaults are insufficient.
- Reuse source-specific patterns only when corresponding requirements are present.
References
- Decision tree:
references/decision-tree.md - Shared verification map:
../_shared/references/verification-sources.md
More from atlanhq/atlan-sample-apps
atlan-fact-verification-gate
Verify Atlan app behavior against SDK docs/code and CLI docs/code before behavior-changing decisions; use lightweight checks by default and deep checks when risk is high.
10atlan-sdk-objectstore-io-defaults
Enforce object store and IO defaults from the Atlan SDK for output paths, prefixes, and file writes. Use when implementing or reviewing raw/transformed output handling.
8atlan-cli-install-configure
Install Atlan CLI with OS-aware binaries (or Homebrew on macOS) only when missing, then configure baseline tenant auth/log settings.
6atlan-cli-run-test-loop
Run Atlan app execution loops using CLI-first commands with automatic CLI availability checks and safe fallbacks.
5atlan-review-doc-sync
Run findings-first review for Atlan app changes and synchronize app documentation with implemented behavior. Use when completing a change set, preparing handoff, or auditing regressions.
5atlan-app-scaffold-standard
Scaffold new Atlan apps from CLI templates as the default behavior when users ask for a new app, then align files to sample-app standards.
5