atlan-sdk-objectstore-io-defaults
Atlan SDK Objectstore IO Defaults
Apply SDK-native defaults for all output read/write logic.
Workflow
- Apply defaults from
references/defaults.md. - Use SDK path-building conventions instead of hardcoded prefixes.
- Route writes through SDK IO abstractions where possible.
- If local SDK checkout is unavailable, verify behavior from installed package source or remote SDK source/docs.
- Run
atlan-fact-verification-gatewhen output behavior changed or conflicts with existing tests. - Validate expected output sections in
e2e_case_contract.yaml.
Non-Negotiable Rules
- Do not hardcode bucket prefixes when SDK-derived paths exist.
- Keep raw and transformed outputs under workflow-specific output path.
- Align output naming with e2e assertions.
References
- Defaults and anti-patterns:
references/defaults.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-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.
5atlan-sql-connector-patterns
Select and apply the correct SQL connector implementation pattern (SDK-default minimal or source-specific custom). Use when building or extending SQL metadata/query extraction connectors.
5