Currently, when huxley remote add [cluster-name] is run on the CLI, the CLI will go into the user's Huxley dotfile and access information stored there about the cluster in question. This is at best fragile, and at worst ineffective if a user tries to add a remote to a cluster they did not personally create (We want to allow access to clusters associated with their organization's account).
On the API server, a record in the cluster collection should have a field storing the public domain that cluster uses. When the command huxley remote add is used, that information can be accessed and added to the configuration object.
@peterlnguyen, this is another CLI ticket I'm assigning to you. The cluster collection will not have a public_domain field until after Alpha 03 is released.
Currently, when
huxley remote add [cluster-name]
is run on the CLI, the CLI will go into the user's Huxley dotfile and access information stored there about the cluster in question. This is at best fragile, and at worst ineffective if a user tries to add a remote to a cluster they did not personally create (We want to allow access to clusters associated with their organization's account).On the API server, a record in the
cluster
collection should have a field storing the public domain that cluster uses. When the commandhuxley remote add
is used, that information can be accessed and added to the configuration object.