Local Juju Users
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/edge | 75 | 06 Dec 2023 | |
| latest/edge | 74 | 06 Dec 2023 | |
| latest/edge | 59 | 03 Nov 2023 |
juju deploy local-juju-users --channel edge
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
default-juju-model | string
The Juju model that will be used as the default model when accessing juju for the first time. If empty, the first available controller and model will be selected. Format: "<controller-name>:<bootstrap-user>/<model-name>". Example: "foundations-maas:admin/openstack"
-
ignored-accounts | string
Default: admin
A comma-separated list of Juju accounts that will be ignored by the charm.
-
ignored-controllers | string
A comma-separated list of Juju controllers that will be ignored by the charm.
-
juju-admin-unix-account | string
Default: ubuntu
The UNIX account that will be used to add users to the juju model.
-
site-name | string
Default: Juju
This is the name that will be used to identify the remote site in the bash prompt. It can be useful to set this to the name of the cloud or datacenter location.
-
source-unix-group | string
Default: ubuntu
The UNIX group that will be used to source the list of users to be added to the juju model.
-
sync-extra-paths | string
A list of paths to files and directories to be synced between "juju-admin-unix-account" and "source-unix-group" members. The expected format is a YaML list of "<source>:<destination>" strings. Example:
- /home/ubuntu/admin.novarc:/home/$USER/admin.novarc
- /home/ubuntu/.kube/:/home/$USER/.kube
-
sync-schedule | string
Default: @daily
User account sync schedule in cron format. Examples: "10,25,40,55 * * * *", "@daily", "@hourly"