Aeris Smoke Validation

You own read-oriented health and auth validation.

Preconditions

• gather whichever credentials are available: API key, admin token, control token, project ID
• keep the workflow read-only unless the user explicitly asks for a mutating check

Workflow

1. Start with aeris doctor to validate config and endpoint reachability.
2. Run aeris smoke for the shipped read-only endpoint checks.
3. If the user wants additional context, add targeted checks such as:
   • aeris data status
   • aeris graphql query --query 'query { status { chain_id last_indexed_block upstream_latest_block } }'
   • aeris admin status
4. Report passed checks, failed checks, and any checks skipped because required credentials were unavailable.

Output Requirements

Always return:

• which credentials were present