[
https://issues.apache.org/jira/browse/PHOENIX-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893750#comment-17893750
]
Istvan Toth edited comment on PHOENIX-7446 at 10/29/24 9:00 AM:
----------------------------------------------------------------
The preset script based solution does the same as increasing TTL, but does not
require setting extremely long TTLs in the config (which are likely to stay
that way)
Not huge deal either way, but I prefer this one.
was (Author: stoty):
This solution does the same, but does not require setting extremely long TTLs
in the config.
Not huge deal either way, but I prefer this one.
> Document GPG passphrase handling in release process
> ---------------------------------------------------
>
> Key: PHOENIX-7446
> URL: https://issues.apache.org/jira/browse/PHOENIX-7446
> Project: Phoenix
> Issue Type: Task
> Reporter: Istvan Toth
> Priority: Major
>
> It seems like the maven GPG plugin is no longer able to ask for a passphrase,
> and it has also been disabled for the tar.gz signing in the release script.
> It seems like we need to somehow preset the passphrase before running the
> release script.
> It seems that this requires either modifying the gpg-agent cache times so
> that it's longer than the release process, or using the gpg-preset-passphrase
> tool.
> Figure this out and document on the release page on the website and/or the
> release script README.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
