infra: update to use ssh keys instead of password for publishing arti…#12497
Open
mahesh-wor wants to merge 2 commits into
Open
infra: update to use ssh keys instead of password for publishing arti…#12497mahesh-wor wants to merge 2 commits into
mahesh-wor wants to merge 2 commits into
Conversation
mahesh-wor
force-pushed
the
infra-ssh-key-support
branch
from
f279636 to
40cf182
Compare
Contributor
Author
|
Following ssh key/username already configured in github action secrets.
existing |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Related Open Issue
#11751
https://github.com/geosolutions-it/support/issues/6199
Description
The goal is to use ssh public keys for authenticating to maven repository. Earlier implementaion of
wagon-sshhas several downsides (eg: no support for newer crpt algo, custom settings.xml, no support of openssh keys etc), hence is replace withwagon-ssh-externalthat uses the host's ssh executeable to perform those actions.Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
Github and Jenkins build/publish jobs uses username/password to authenticate to maven repository.
What is the new behavior?
Use of ssh-keys for authentication to maven repository with
wagon-ssh-externalplugin and updated github actions.Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Rollback
Rollback would include reverting the PR, that should enable existing
user/password basedworkflow. As a precaution existing secrets are left intact and to be deleted only when ssh-key based workflow is working.