-
-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support ipv6 for scp with "none" backend #1006
Conversation
I had this patch applied on top of
|
Looks like another |
I observed the regression with the hetzner provider, didn't test deploying secrets with the 'none' provider so far.
|
Ah, okay, I need to update the signature to I'll update this PR in the next days. In the meantime, just update |
Looking at the other implementations of |
Yup, I had the same thought. I'm quite busy right now, but I'll try to update this PR in the next weeks. It's not like it hasn't been lying around for a while already ;) |
Sure, whenever you find the time :-) |
@phryneas - poke, could you update this PR? |
@flokli oops, sorry. There you go. |
LGTM. CI is red due to the current nixpkgs breakage with azure-mgmt-compute-4.4.0 (unrelated, fixed by NixOS/nixpkgs#56775). |
Motivation:
Currently, secrets cannot be deployed when
deployment.targetHost
contains an ipv6.This is because, while sshing to a ipv6 has the same syntax,
scp
requires square brackets around the ip. This adds square brackets for calls to scp around any ip with a colon.I'm no python developer, so please take this PR with a grain of salt. Fortunately, it's not very big ;)