atlan-sdk-objectstore-io-defaults

Enforce output paths by applying SDK IO defaults that align outputs with the standard structure: artifacts/apps/<application_name>/workflows/<workflow_id>/<run_id>. This ensures consistency across raw and transformed outputs and enables end-to-end contract validation.

Raw outputs are stored under the raw directory for unprocessed data, while transformed outputs go under transformed for processed results. SDK IO defaults automate this separation to maintain consistent artifact naming and layout across workflows.

Hardcoded prefixes break consistency, complicate artifact validation, and make workflows fragile across environments. Using SDK IO abstractions replaces hardcoded values with configurable defaults, ensuring reliable end-to-end validation and standardized artifact structure.

Review raw and transformed output implementations to identify hardcoded paths and prefixes, then replace them with SDK IO defaults. This skill guides teams through audit workflows to enforce consistent naming and validate artifact layout against SDK conventions.

Yes. SDK IO defaults apply universally across apps and workflows by using dynamic path placeholders like application_name, workflow_id, and run_id. This approach scales consistency across all workflows and applications in your infrastructure.