Configuration

Configuration

mqgov contexts bind commands to one backend: Kafka, RabbitMQ, Pulsar, or RocketMQ.

Contexts

mqgov ctx set <name> --backend kafka --brokers <h:p,h:p> [--sasl-mechanism PLAIN] [--tls --ca-cert <f>] [--schema-registry-url <url>]
mqgov ctx set <name> --backend rabbitmq (--amqp-url <url> | --host <h> --port <p> --vhost </>) --management-url <url> --username <u>
mqgov ctx set <name> --backend pulsar --service-url pulsar://<h:p> --admin-url http://<h:p> [--tenant public] [--pulsar-namespace default]
mqgov ctx set <name> --backend rocketmq --nameservers <h:p,h:p> [--broker-addr <h:p>]
mqgov ctx use <name>
mqgov ctx list -o json
mqgov ctx test -o json

Credentials

Use credential backends for stored secrets. RabbitMQ non-interactive runs can use:

export MQGOV_PASSWORD='***'

Schema registry passwords and broker passwords should use --credential-backend encrypted-file|keychain|...; non-plain backends are required for persisted secrets.

Portable Contexts

mqgov ctx export <name> -o json
mqgov ctx import -f ctx.yaml --overwrite -o json
mqgov ctx migrate-credentials --dry-run
mqgov ctx migrate-credentials --yes

Roles

mqgov ctx role set <context> --target-operator alice --role writer -o json
mqgov ctx role list <context> -o json