trustpub/tokens/exchange: Implement GitLab CI support #12026
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.
This PR adjusts our
POST /api/v1/trusted_publishing/tokens
endpoint to also accept GitLab OIDC tokens.As discussed in #11988, we are using a trust-on-first-use principle for the namespace IDs for GitLab due to some API constraints. In other words: the token exchange endpoint will fill in the
namespace_id
column from the OIDC JWT claims if it was empty before and on each subsequent token exchange it will only accept it if the IDs are matching.Other than that, this is essentially the same implementation as for GitHub Actions.
Worth noting also is that, just like PyPI, we only support gitlab.com for now, but not any self-hosted GitLab instances.
Related