A Juju credential represents a collection of authentication material (like username & password, or client id & secret key) that is specific to a cloud and that allows Juju to interact with that cloud.
Clouds can have one or more sets of credentials associated with them. Each model created in Juju is associated with a cloud/credential pair for the model to create resources on the underlying cloud. For more information on models see Model.
A credential is managed by means of a user-defined name—the credential name.
Juju credentials can be created for either the Juju client or the Juju controller or both – where a client credential denotes a credential that the client is aware of and a controller credential denotes a credential that a controller is aware of.
When you bootstrap a controller and use a ‘client credential’, this credential gets automatically uploaded to the controller, so it becomes a ‘controller credential’ also. For this reason, the set of client credentials and controller credentials can end up being the same. However, they don’t have to.
A client credential and a controller credential have also been called a “local” credential and, respectively, a “remote” credential.
Last updated 11 days ago.