def add_args(self, parser: configargparse.ArgumentParser) -> None:
_aptly_args.add_shared_args(parser)
gp_ast = parser.add_argument_group("Aptly Store options")
gp_ast.add_argument("--aptly-distribution", dest="aptly_distribution", default="", env_var="APTLY_DISTRIBUTION",
help="Set the target distribution for aptly builds.")
gp_ast.add_argument("--aptly-repo-opts", dest="aptly_repo_opts", default="", env_var="APTLY_REPO_OPTS",
help="Specify additional command-line parameters which will be appended to every "
"'aptly repo' command executed by the Aptly Store.")
gp_ast.add_argument("--aptly-publish-opts", dest="aptly_publish_opts", default="", env_var="APTLY_PUBLISH_OPTS",
help="Specify additional command-line parameters which will be appended to every "
"'aptly publish' command executed by the Aptly Store.")
gp_ast.add_argument("--aptly-publish-endpoint", dest="aptly_publish_endpoint", metavar="ENDPOINT", default=None,
env_var="APTLY_PUBLISH_ENDPOINT",
help="Publish the Aply repo to the specified endpoint after generated packages have been "
"added to the repo. Please note that you will have to add additional configuration to "
"the aptly config file, for example when you want to publish to S3. It's also likely "
"that you want to set --aptly-publish-opts and pass aptly -passphrase-file, -keyring "
"and other necessary arguments for signing the repo. Please note: You will probably "
"want to set these arguments using environment variables on your build server if "
"you're using a CI environment.")
gp_ast.add_argument("--aptly-dont-remove", dest="aptly_dont_remove", action="store_true", default=False,
env_var="APTLY_DONT_REMOVE",
help="By default, if a created package already exists in the repo specified by --repo, "
"the aptly store will overwrite it. Setting --aptly-dont-remove will instead lead "
"to an error if the package already exists.")
gp_ast.add_argument("--aptly-overwrite-newer", dest="aptly_overwrite_newer", action="store_true", default=False,
env_var="APTLY_OVERWRITE_NEWER",
help="If set, the aptly Store will store newly generated packages in the repo which are "
"older than the packages already there. By default, it will raise an error message "
"instead.")
gp_ast.add_argument("--aptly-passphrase", dest="aptly_passphrase", env_var="APTLY_PASSPHRASE", default=None,
help="Set this to pass the GPG signing passphrase to the aptly Store. This is primarily "
"useful when you use the environment variable. This way your build server can read "
"the passphrase from secure storage it pass it to GoPythonGo with a modicum of "
"protection. Using the command-line parameter however will expose the passphrase to "
"every user on the system. You're better of passing --passphrase-file to aptly via "
"--aptly-publish-opts in that case. The most secure option would be to use "
"--use-aptly-vault-wrapper.")
gp_ast.add_argument("--use-aptly-vault-wrapper", dest="use_aptly_wrapper", env_var="APTLY_USE_WRAPPER",
default=False, action="store_true",
help="When you set this, GoPythonGo will not directly invoke aptly to publish or update "
"aptly-managed repos. Instead it will call GoPythonGo's vault_wrapper program in"
"'aptly' mode, which can be configured by environment variables or its own "
"configuration file or both (Default: .gopythongo/vaultwrapper). This program will "
"load the GnuPG signing passphrase for aptly-managed repos from Hashicorp Vault. You "
"can find out more by running 'vaultwrapper --help'.")
评论列表
文章目录
