UaaS CLI problems and fixes

Confirm environment, product permission and current service authority. A usable credential and healthy service do not grant every operation. Current access can be denied or temporarily unverifiable; resolve that with the service owner. An interrupted response does not undo a committed write.

Read the exact product, release or key state before retrying. Nonzero status does not prove no change. Product create/show and key rotate may omit details; read product or key list. Repeating rotation or promotion can perform another change.

Compare the draft with the approved support matrix and latest active release. Supply missing approved builds. Use the paired platform-drop override and reason only for an approved retirement; do not withdraw an existing release to evade the comparison. Use upgrade or full for --update-type despite the stale help hint.

Confirm the unchanged source file, release identity, channel and expected checksum. Chunk retry can resume a matching session, but expiry or finalization failure may require a fresh transfer. Do not execute incomplete downloads or bypass signature/checksum checks; an older destination can remain after failure.

Inspect the complete result and ask the installation owner to apply the release. uaas update requires an interactive terminal when an offered update needs approval; there is no force flag. A late cache-write failure can leave stage files. Startup does not install them; confirm version and an authorized read after replacement.

Run uaas doctor and inspect failed, warning and skipped checks. The command is non-strict, cached observations may be old, and a healthy connection is not permission. Keep codes, private keys and full credential contents out of support reports.