Conversation
… The remote is the first part of the unit name - the end of the name is demmarked by a colon (`:`). If no remote is specified the default local bravetools remote is used.
…h remote has its own profile associated with it, including bravetools local remote. If no profile specified through CLI or in Bravefile itself, the remote profile will be used.
|
This looks really nice - Would be good to have a nice mechanism of creating remotes directly through bravetools without manual copy of certs. Thoughts? |
Yes, I think we can provide a CLI command that will automatically create and authenticate with a remote if that LXD server is configured with a Trust password and you have that password. |
…Avoiding attempting to add cert to server that already trusts bravetools.
…vetools remotes. Enables adding/deleting/getting/listing remotes through CLI rather than manually creating config files and authenticating by hand.
Remote cli
Added remote management through CLI in latest commits. The commands enable add/get/remove/list operations on remotes. When adding new remotes authentication can be handled by bravetools if providing a trust password. |
Enables users to specify the remote to deploy to using the unit name. The first section of the unit named preceding the colon ":" will be taken as the remote name. If no remote is specified the default bravetools local remote will be used.
For example, the following Bravefile snippet will deploy a unit called "example" at the "test" remote:
Also included in this is a way to specify which LXD profile to deploy the unit using, since we can no longer assume the local profile will exist on remotes. This profile can be specified in the Bravefile Service section or using a CLI flag
brave deploy --profile [name]. If no profile is specified, the remote's default profile saved at ~/.bravetools/remotes will be used.