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.
At time of writing, the v2 branch has a
However, there's no specific way of organizing or labeling
Put another way, unless you're rolling purely with the API, having Group objects lying around somewhere is useless if the CLI or task-calling bits have no way of finding them!
In v1, roles were effectively a single flat namespace mapping simple string labels to what would be Groups in v2, and they could be selected on the CLI at runtime (
Users defined them in
Specific use cases / needs / subfeatures
From the mailing list:
Our use cases are:
For Fabric v2 to become useful to me, I would need a way to tell
Previously I defined roles and then ran
I fail to find an equivalent in Fabric v2, and I also failed to emulate this feature using:
active_hostset: null hostsets: myhostset: - ...
Instead of the expected list of hosts I get
We map different sets of hosts to each role for each of our environments in fabric v1, and the environment is set by running a
In v2 we tried using a custom Task, but the problem is
I prototyped this in my forks: