'juju add-credential' operates on local cache only. It does not really matter to Juju if it is valid, besides there is no guarantee that Juju has access to the cloud to verify the credential before we have a bootstrapped system. There is no strict limitations on user - credential can be added locally before a cloud is, for example.
However, the validation will definitely take place when a credential will be in used. For ***local*** (client side) credentials, this will take place when a user either bootstraps or adds a new model with that credential. For ***remote** (server side) credential that will happen during the upload.
'juju add-credential' operates on local cache only. It does not really matter to Juju if it is valid, besides there is no guarantee that Juju has access to the cloud to verify the credential before we have a bootstrapped system. There is no strict limitations on user - credential can be added locally before a cloud is, for example.
However, the validation will definitely take place when a credential will be in used. For ***local*** (client side) credentials, this will take place when a user either bootstraps or adds a new model with that credential. For ***remote** (server side) credential that will happen during the upload.