ezgh hosted-queues users create <cluster> <name> [--preset p | --vhost name=preset | --permissions json] [--wait] [flags]Create a user. Its password is generated and written to a new Secret in the project, which users get names; ezgh never prints it. Without permissions a Kafka user is readWrite. Kafka users take --preset: admin (every topic and group; create, delete and configure topics), readWrite (produce and consume every topic, every group, create topics) or readOnly (consume). RabbitMQ users take --vhost name=readWrite or name=readOnly, once per vhost. Custom grants go in --permissions, the API’s JSON: Kafka {“preset”:“custom”,“topics”:[{“topic”:“orders.*”,“access”:“produceConsume”,“create”:true}], “groups”:[{“group”:“workers-*”}]}; RabbitMQ {“vhosts”:[{“vhost”:“app”,“preset”:“custom”,“configure”:“^$”,“write”:“^jobs”,“read”:“.*”}]}.
Part of ezgh hosted-queues users.
Examples
ezgh hosted-queues users create events snuba --preset admin --wait
ezgh hosted-queues users create jobs worker --vhost /=readWrite --waitFlags
| Flag | Type | Default | Description |
|---|---|---|---|
--permissions |
string | the permissions as the API’s JSON, for custom grants (see --help) |
|
--preset |
string | Kafka: admin, readWrite or readOnly | |
--vhost |
string, repeatable | RabbitMQ: a vhost and its preset, name=readWrite or name=readOnly (/ is the default vhost); repeat for more | |
--wait |
boolean | wait until it’s available, and print it then | |
--wait-timeout |
duration | 10m0s |
how long --wait waits |
This command also takes the global flags.