When configuring a material backed by Git, such as GitHub.com or GHE, the user story for non-public repositories is unpleasant, GoCD is built for the world where nobody keeps a git repo private so there's no server-level push for personal access tokens _nor_ is there the ability to encrypt API credentials/tokens in material definitions.
Users end up having to either:
Proposed changes:
Anyone got thoughts on this?
Sort of related to #951, #430 and #1323. Needs some PR love. I'd suggest thinking about more generic SSH key support (ala #430), because that will support git:// URLs as well as svn+ssh://, ssh://[email protected]... and everything else.
Some of what you've mentioned is related to #1696 as well. So, maybe @ketan has some thoughts.
Lacking this feature makes it a no-go. Simple config of ssh-keys is a minimum requirement of modern CI/CD tools.
GoCD now has secrets management support, which makes this a little better (can parameterize SSH keys and tokens externally). I understand it is not perfect and seamless.
Most helpful comment
Lacking this feature makes it a no-go. Simple config of ssh-keys is a minimum requirement of modern CI/CD tools.