fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534)

~1500 progress messages across 481 files were using log_warn (yellow)
for normal status updates like "Installing...", "Setting up...",
"Creating server...", etc. This made users think something was wrong
when everything was proceeding normally.

Changes:
- Replace log_warn with log_step for all progress/status messages
- Keep log_warn only for actual warnings (errors, remediation hints)
- Remove emoji from 3 sprite completion messages

Agent: ux-engineer

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
This commit is contained in:
A 2026-02-11 14:37:43 -08:00 committed by GitHub
parent 800e9ed564
commit 0835b35a36
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
481 changed files with 1602 additions and 1602 deletions

View file

@ -90,7 +90,7 @@ create_server() {
validate_resource_name "${machine_type}" || { log_error "Invalid GCP_MACHINE_TYPE"; return 1; }
validate_region_name "${zone}" || { log_error "Invalid GCP_ZONE"; return 1; }
log_warn "Creating GCP instance '${name}' (type: ${machine_type}, zone: ${zone})..."
log_step "Creating GCP instance '${name}' (type: ${machine_type}, zone: ${zone})..."
local userdata
userdata=$(get_cloud_init_userdata)
@ -165,7 +165,7 @@ interactive_session() {
destroy_server() {
local name="${1}"
local zone="${GCP_ZONE:-us-central1-a}"
log_warn "Destroying GCP instance ${name}..."
log_step "Destroying GCP instance ${name}..."
gcloud compute instances delete "${name}" --zone="${zone}" --project="${GCP_PROJECT}" --quiet >/dev/null 2>&1
log_info "Instance ${name} destroyed"
}