COA Doctor
coa_doctorDiagnose and verify local COA project setup by validating data.yml, workspaces.yml, credentials, and warehouse connectivity.
Instructions
Run coa doctor against a local COA project — checks data.yml, workspaces.yml, credentials, and warehouse connectivity.
KNOWN ISSUE (CD-16983): doctor reports the profile selected via workspaces.yml / --workspace, but coa_plan / coa_deploy / coa_refresh resolve profile differently — they fall through to the [default] profile in ~/.coa/config unless --profile or COALESCE_PROFILE is set. A green doctor result does NOT guarantee that plan/deploy will authenticate against the same cloud account. When a user reports plan/deploy auth mismatches, suspect profile divergence before blaming credentials. Platform fix approach still under discussion.
Args:
projectPath (string, required): Path to the COA project root (directory with data.yml)
workspace (string, optional): workspaces.yml workspace name (default: dev)
Returns: { command, exitCode, stdout, stderr, timedOut, json?, coaVersion, preflightWarnings? }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workspace | No | COA workspace name from workspaces.yml. Defaults to 'dev'. | |
| projectPath | Yes | Absolute or relative path to the COA project root (the directory containing data.yml). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| json | No | ||
| stderr | Yes | ||
| stdout | Yes | ||
| command | Yes | ||
| exitCode | Yes | ||
| timedOut | Yes | ||
| coaVersion | Yes | ||
| jsonParseError | No | ||
| preflightWarnings | No |