Conversation
|
@tphoney can you take a look? |
| if p.Build.SSHAgent != "" { | ||
| // TODO check in with one of the drone devs...this should not be necessary. I'm probably doing something | ||
| // wrong with the cli framework | ||
| p.Build.SSHAgent = strings.TrimSuffix(p.Build.SSHAgent, "]") |
There was a problem hiding this comment.
Not sure what I'm missing here @tphoney -- I'm getting my values for this flag wrapped in []
|
Hi @bkk-bcd, We really appreciate the effort you've put into this PR, and it's something we would like to support in Drone. We plan to implement this is a slightly different way. We will be using your PR as a guide. I've added this is an item to our backlog, and will prioritize it based on the overall vision of CI & Drone at Harness. In the meantime you can continue to use the fork and decide whether you would like to use our implementation when it's released in the future. Again thanks for the effort, much appreciated! |
|
Look forward to seeing that happen, hopefully soon 😉 |
|
@RickCraig did a solution for this get incorporated into drone master? |
|
@thematrixdev the comments in #382 might help |

Fixes merge conflicts and defects in #336
Will enable https://docs.docker.com/develop/develop-images/build_enhancements/#using-ssh-to-access-private-data-in-builds
For example with the following starlark snippet:
And using the following Dockerfile:
Please note as in this example its expected that a private, base64 encoded, ssh key is provided in the
SSH_KEYenvironment variable. You should use drone secret mechanisms accordingly.