I think it’s great that the
fly CLI will be able to target teams within a target. In general though, I am a bit worried about what happens to “targets” (
-t) more mid/long-term.
I love that concourse switched from team-based to user-based, so I can be logged into many teams at once. The
-t parameter always targeted a single team (as you specify it during the
login command). How will this change in the future? If this is one of the early steps to rework
-t, brilliant, count me in. If this is meant to co-exist over a long time though, I’m worried about explaining this to my users.
In an ideal world, I would want
-t to represent the cluster that I am targeting, and then use the
--team flag to run commands against teams (caveat: commands will get longer? Can we specify a
--default-team with a target?).
For some context, we have around 400-500 developers working with concourse from a regular basis to “maybe once a month”. Concourse and the CLI have a fair bit of a steep learning curve, and having to explain to my devs that you log in to a single team, but then can target other teams with the same target again is going to be very confusing.
Sorry for straying quite a bit off topic here, but if there’s any higher-level story/epic to this it would be awesome if it could be linked; I’m just worried about the complexity of the
As for your question, is there a way to implement this without breaking backwards-compatibility? We provide boilerplate Makefiles to our team that use the hijack commands and it would not be great if all of them had to be changed.