Classify invalid delivery destinations during preflight
This commit is contained in:
@@ -170,9 +170,10 @@ both credential sources, returns status 2. Omission of `token_file` retains
|
||||
environment-only loading.
|
||||
|
||||
After resolving the token, delivery performs an authenticated, read-only
|
||||
repository access check. Missing or rejected credentials, known insufficient
|
||||
permissions, and inaccessible destinations are configuration/credential
|
||||
failures. An unavailable service or canceled check is an operational failure.
|
||||
repository access check. Invalid destination settings, missing or rejected
|
||||
credentials, known insufficient permissions, and inaccessible destinations are
|
||||
configuration/credential failures. An unavailable service or canceled check is
|
||||
an operational failure.
|
||||
See the [CLI contract](cli.md) for exact exit statuses. Successful preflight
|
||||
confirms authentication and repository access and accounts for any exposed
|
||||
delivery-permission deficiency. It does not guarantee later release or asset
|
||||
|
||||
Reference in New Issue
Block a user