Allow specifying transport config (e.g. LXD remote) at the command line

[dontlaugh]

Use Case

I would like to target LXD remotes without using an inventory file. This is possible for some transports, like SSH, but not LXD.

Describe the Solution You Would Like

One way to do this is to change the interpretation of "host:port" syntax, if and only if --transport lxd is provided.

% bolt command run --transport lxd -t edge:proxy-1 uptime
Could not parse target URI: Invalid port number: "proxy-1"

Perhaps, in the case of LXD, this would be interpreted as remote:instance. This would rhyme with the behavior of lxc, as well, which uses the same syntax to prefix instances/containers with a remote.

% lxc exec edge:proxy-1 -- uptime
 00:11:09 up  1:28,  0 users,  load average: 0.01, 0.08, 0.04

Describe Alternatives You've Considered

If we are uncomfortable with magic parsing of bolt's target, perhaps transport configurations could be specified a different way, with a dedicated flag.

--transport-config lxd.remote=edge

or the shorter

-T lxd.remote=edge

If yall are willing to use up one of your precious short flags :)

[dontlaugh]

This would impact this issue, as well martezr/packer-plugin-bolt#1

Using bolt for packer builds isn't really something that inventory is usable for. Right now SSH transport is supported, but allowing other transports would be facilitated by specifying transport configs at the command line.

[github-actions]

This issue has not had activity for 60 days and will be marked as stale.
If this issue continues to have no activity for 7 days, it will be closed.

[github-actions]

This issue is stale and has been closed. If you believe this is in error,
or would like the Bolt team to reconsider it, please reopen the issue.