Atlan Workflow Args Secrets State
Keep workflow and activity data flow aligned with SDK patterns.
Workflow
- •Read
references/state-flow.md. - •Ensure workflow args are loaded through SDK-supported state path.
- •Replace direct credential payload handling with
credential_guid+ secret retrieval. - •Keep
get_workflow_argsfocused on args retrieval/normalization. - •Keep business transformation and artifact writes in dedicated activity methods orchestrated by workflow.
- •Persist workflow state through SDK-compatible state store APIs.
- •Run
atlan-fact-verification-gatefor any workflow lifecycle change that can affect runtime behavior. - •Reflect this behavior in e2e contracts and loop reports.
Rules
- •Never persist raw secrets in workflow args snapshots.
- •Never bypass state store for cross-activity workflow state.
- •Keep retries/timeouts aligned with workflow conventions.
- •Do not collapse the full business pipeline into
get_workflow_argsside effects.
References
- •State flow map:
references/state-flow.md - •Shared artifacts:
../_shared/references/artifact-templates.md