docs(secrets): document secret set readiness and async provisioning#801
Merged
Conversation
The API now treats secret-set provisioning as asynchronous and exposes
a per-set readiness status (ready / pending / failed) on GET responses.
Deploys that bind a secret set or image pull secret are gated on the
ready state and rejected with 409 Conflict otherwise.
- Fundamentals: add a "Provisioning and readiness" section to
secrets.mdx and a 409-deploy entry in error-codes.mdx.
- REST reference: PUT /secrets/{setName} returns 202; add 409 for
concurrent modification; GET single + list responses include the new
status and errorMessage fields.
- CLI reference: note the readiness state shown in `pcc secrets list`,
and that `--secrets`, `--credentials`, `secret_set`, and
`image_credentials` must reference a ready set.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Author
|
This is good to merge now, the corresponding changes are live in prod. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The API now treats secret-set provisioning as asynchronous and exposes a per-set readiness status (ready / pending / failed) on GET responses. Deploys that bind a secret set or image pull secret are gated on the ready state and rejected with 409 Conflict otherwise.
pcc secrets list, and that--secrets,--credentials,secret_set, andimage_credentialsmust reference a ready set.