using-cloud-cli

# Cloud CLI Patterns Credentials may be pre-configured. Verify identity before touching resources. Use `--help` or `looking-up-docs` for syntax. ## Safety and Identity Before destructive commands (`delete`, `destroy`, `rm`, `terminate`, IAM changes, bucket/object deletion): Do not present executable delete commands as the next action until identity and candidate resources have been shown and the user has explicitly confirmed the exact resources. A safe answer may show inventory/dry-run commands first, then say deletion commands come only after confirmation. 1. Confirm the active cloud target: - AWS: `aws sts get-caller-identity` plus explicit `--profile` and `--region` when relevant. - GCP: `gcloud config get-value account` and `gcloud config get-value project`, or pass explicit `--project`. 2. Inventory candidate resources with non-destructive list/describe commands. 3. Present the exact command, account/profile, project, region/zone, and resources affected. 4. Require explicit user confirmation before execution. Do not rely on `--quiet`, default profiles, or implicit projects for destructive work. ## BigQuery ```bash # Always estimate cost first bq query --dry_run --use_legacy_sql=false 'SELECT ...' # Run query bq query --use_legacy_sql=false --format=json 'SELECT ...' # List tables bq ls project:dataset # Get table schema bq show --schema --format=json project:dataset.table ``` **Cost awareness**: Charged per bytes scanned. Use `--dry_run`, partition table...