-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-24572 release scripts should try to use a keyid when refering to GPG keys. #2001
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
So it makes a guess, but that guess is not correct in my case. I want it to use the dedicated signing key ( |
| [ -z "${GPG_KEY_ID}" ] ; then | ||
| GPG_KEY_ID=$("${GPG}" "${GPG_ARGS[@]}" --keyid-format 0xshort --list-public-key "${GPG_KEY}" | head -n 1 | grep -o "0x[0-9A-F]*" || true) | ||
| fi | ||
| read -r -p "We think the key '${GPG_KEY}' corresponds to the key id '${GPG_KEY_ID}'. Is this correct [y/n? " ANSWER |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing closing brace on [y/n?
|
What am I saying, it has chosen the key I intended. |
|
the former is the 0xlong key id and the latter is the 0xshort key id. if you gave the 0xlong key id in the |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
first pass at turning a given gpg key name into a key id during release info gathering.