Transport configuration(s)

[dontlaugh]

I use Bolt's LXD transport https://puppet.com/docs/bolt/latest/bolt_transports_reference.html

It looks like this project only supports SSH and WinRM. Would you accept the LXD transport as a contribution?

There's also docker and podman, which I don't use but which might be nice.

Each of the configuration options of alternative transports might evolve on their own path, so we'd have to consider how to handle the config.

[martezr]

@dontlaugh I'd be open to accepting an LXD transport contribution. The thought that comes mind would be adding a new transport block.

transport {
   type     = "lxd"
   run_as = "root"
}

I'd have to mock up what that actually looks like but could be a possible option. I might take a look at the Docker transport as a foundation while the LXD transport is being worked.

[dontlaugh]

Is there a chance you'll have to deal with transport configs that contain a little bit of nesting?

Perhaps we should make the config portion a generic map? If the hashicorp code generator supports it.

transport {
  type  = "native-ssh"
  config = {
    public_key = "..."
    private_key = "..."
  }
}

Alternative: the more verbose and strongly-typed (but maybe easier on the business logic side)

transport {
  native_ssh {
    public_key = "..."
    private_key = "..."
  }
}

In your code we could enforce the invariant that only one transport could be configured by serializing the NativeSSH config struct as a pointer or something. 🤔

---

On my team, we already use the lxd builder for baking images, but we only use the "file" and "shell" and "shell-local" provisioners.