We need to update the help text, because I'm pretty sure it is "juju bootstrap --agent-version X" rather than "--config" at this point.
As for RC vs Stable, we still have the bug where if you're using a 'devel' version (anything with an 'rc/beta/etc' then it only sees beta agents as targets for deploy).
Also for *bootstrap* people have generally pushed pretty hard that we have to bootstrap the exact version as the client, and then possibly 'upgrade' to the requested version. And since you're using a newer client, we probably wouldn't let you downgrade the controller anyway.
(For example, 2.2 breaks bootstrap wrt 2.1 because it added a new mandatory field, so a 2.1 client couldn't bootstrap a 2.2 agent anyway, you have to go through the upgrade step.)
I think the docs we could fix, actually selecting the agent version is a bit trickier to support in all cases.
Generally within .patch versions, we could probably do it, but major.minor is probably not ever really supported.
We need to update the help text, because I'm pretty sure it is "juju bootstrap --agent-version X" rather than "--config" at this point.
As for RC vs Stable, we still have the bug where if you're using a 'devel' version (anything with an 'rc/beta/etc' then it only sees beta agents as targets for deploy).
Also for *bootstrap* people have generally pushed pretty hard that we have to bootstrap the exact version as the client, and then possibly 'upgrade' to the requested version. And since you're using a newer client, we probably wouldn't let you downgrade the controller anyway.
(For example, 2.2 breaks bootstrap wrt 2.1 because it added a new mandatory field, so a 2.1 client couldn't bootstrap a 2.2 agent anyway, you have to go through the upgrade step.)
I think the docs we could fix, actually selecting the agent version is a bit trickier to support in all cases.
Generally within .patch versions, we could probably do it, but major.minor is probably not ever really supported.