Skip to main content

astroctl_cloud_gcp_selfHosted_validate

astroctl cloud gcp selfHosted validate​

Pre-flight validation of GCP self-hosted prerequisites

Synopsis​

Validate that all prerequisites are in place for self-hosted cluster provisioning.

Checks:

  • Credentials are valid and can authenticate
  • Project is accessible
  • Required APIs are enabled
  • Required IAM roles are assigned
  • GCS bucket exists and is accessible

Credentials are resolved in this order:

  1. Explicit --credentials flag (file path, raw JSON, or base64)
  2. GOOGLE_APPLICATION_CREDENTIALS environment variable
  3. GOOGLE_CREDENTIALS environment variable (raw JSON)
  4. Application Default Credentials (gcloud auth application-default login)

All checks run to completion even if some fail, so you can see everything that needs to be fixed in a single pass.

astroctl cloud gcp selfHosted validate [flags]

Examples​

  # Validate with auto-detected credentials (from env or application default)
  astroctl cloud gcp selfHosted validate --project-id my-proj --bucket my-bucket

  # Validate with credential file
  astroctl cloud gcp selfHosted validate --project-id my-proj \
      --credentials /path/to/key.json --bucket my-bucket

  # Validate with base64-encoded credentials
  astroctl cloud gcp selfHosted validate --project-id my-proj \
      --credentials "$(base64 key.json)" --bucket my-bucket

Options​

      --bucket string        GCS bucket name for cluster state (required)
      --credentials string   Path to GCP service account JSON key, raw JSON, or base64-encoded JSON (optional — auto-detected if not provided)
  -h, --help                 help for validate
      --project-id string    GCP project ID (required)

Options inherited from parent commands​

  -o, --output string   Output format (json|yaml) (default "yaml")

SEE ALSO​