Skip to main content

Global Flags

Flags available on all asc commands for authentication, debugging, and reporting
Global flags are available on all asc commands and control cross-cutting concerns like authentication, logging, and CI reporting.

Authentication Flags

--profile

Use a named authentication profile stored in your keychain or config file.
Environment variable: ASC_PROFILE See also: Authentication Guide

--strict-auth

Fail when credentials are resolved from multiple sources (e.g., both environment variables and keychain).
Default: false Environment variable: ASC_STRICT_AUTH (accepts true/false, 1/0, yes/no, y/n, on/off) This flag helps catch configuration issues where credentials might be coming from unexpected sources.

Debug and Logging Flags

--debug

Enable debug logging to stderr for troubleshooting CLI behavior.
Environment variable: ASC_DEBUG=true Outputs detailed information about:
  • Command parsing and execution
  • Authentication resolution
  • API request preparation
  • Response processing

--api-debug

Enable HTTP debug logging to stderr, showing full request and response details.
Environment variable: ASC_DEBUG=api Outputs:
  • HTTP request method, URL, headers, and body
  • HTTP response status, headers, and body
  • Sensitive values are automatically redacted (API keys, tokens, etc.)
Useful for:
  • Debugging API integration issues
  • Understanding rate limiting
  • Inspecting response payloads
  • Troubleshooting authentication failures

--retry-log

Enable retry logging to stderr to see when the CLI automatically retries failed requests.
Environment variable: ASC_RETRY_LOG=true Outputs information about:
  • Retry attempts and backoff delays
  • Transient error conditions
  • Rate limit handling
Note: This flag overrides ASC_RETRY_LOG and config file settings when explicitly set.

CI and Reporting Flags

--report

Report format for CI output. Currently supports junit for JUnit XML test reports.
Valid values: junit Required: --report-file must be specified when using --report Use this in CI pipelines to generate test reports that integrate with CI platforms like Jenkins, GitHub Actions, or GitLab CI.

--report-file

Path to write CI report file (used with --report).
Required: --report must be specified when using --report-file

Version Flag

--version

Print version information and exit.
Default: false Outputs the current CLI version. Useful for:
  • Verifying installation
  • Troubleshooting compatibility issues
  • Including version info in bug reports

Flag Behavior

Flag Placement

Global flags must appear before the top-level command:

Flag Priority

When the same setting is configured in multiple places, the CLI uses this priority order (highest to lowest):
  1. Explicit command-line flags
  2. Environment variables
  3. Profile-specific config file settings
  4. Global config file settings
  5. Built-in defaults

Boolean Flags

Boolean global flags (--debug, --api-debug, --retry-log, --strict-auth, --version) can be used without values:

Environment Variables

All global flags have corresponding environment variables for easier configuration in CI or development environments:

Additional Environment Variables

These environment variables don’t have corresponding flags but control global behavior:

Examples

Development Workflow

CI Pipeline

Debugging

See Also