Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Consider reinstating --gateway in v2 somehow #1806
In v1, the
In v2, the
What this means is that v2 lost the ability to specify a ProxyJump style gateway at runtime; the only current possibility is to do eg
It'd be nice to address this, but doing so does require leaning more heavily on string-to-object shorthand. We do retain that to some degree (the first arg to Connection can resemble v1 host strings) so it's possible, just not 100% ideal.
More importantly is just the split between the two gateway styles; if we want to do this properly we need two CLI flags so we can tell exactly what the user intends, otherwise it's ambiguous ("ok, we parsed the CLI, and we have a gateway string. should we be trying to make a Connection out of it or no?").
FWIW - given we have SSH config support and other strong (including Python-format) configuration file support, and that one's need to use a gateway is usually not something that changes minute to minute, this feels low priority to me considering it's a nontrivial bit of work and extra CLI args. So I'm not putting it in any milestones yet.
We're in the process of upgrading to Fabric 2.x and we hit this issue. We're trying to work around the issue or patch in support for
Just thought I'd leave a note here since it's documented as something you might consider adding if users actually notice the lack of the feature.