actions/pypi-publish
1
0
Fork 0
mirror of https://github.com/pypa/gh-action-pypi-publish.git synced 2024-09-17 18:17:07 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #142 from trail-of-forks/tob-indicate-oidc

Browse source 
Add explanation of why the OIDC publishing was chosen to the log output.
This commit is contained in:
Sviatoslav Sydorenko 2023-04-03 02:07:09 +02:00 committed by GitHub
commit 69efb8cbfb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
oidc-exchange.py
View file

@ -17,6 +17,12 @@ Trusted publisher (OIDC) exchange failure:
{message}
You're seeing this because the action wasn't given the inputs needed to
perform password-based or token-based authentication. If you intended to
perform one of those authentication methods instead of trusted
publishing, then you should double-check your secret configuration and variable
names.
Read more about trusted publishers at https://docs.pypi.org/trusted-publishers/
"""

3
twine-upload.sh
View file

@ -46,7 +46,8 @@ if [[ "${INPUT_USER}" == "__token__" && -z "${INPUT_PASSWORD}" ]] ; then
echo \
'::notice::Attempting to perform OIDC credential exchange' \
'to retrieve a temporary short-lived API token for authentication' \
"against ${INPUT_REPOSITORY_URL}"
"against ${INPUT_REPOSITORY_URL} due to __token__ username with no" \
'supplied password field'
INPUT_PASSWORD="$(python /app/oidc-exchange.py)"
elif [[ "${INPUT_USER}" == '__token__' ]]; then
echo \