Releases: JiangHe12/mqgov-cli
Releases · JiangHe12/mqgov-cli
Release list
v0.5.10
v0.5.9
Changed
- CLI-owned environment variables now prefer the family-standard
MQGOV_*names:MQGOV_AUDIT_PRIVATE_KEY,MQGOV_CREDENTIAL_PASSPHRASE,MQGOV_OPERATOR,MQGOV_DOWNLOAD_MIRROR, andMQGOV_SKIP_VERIFY. DeprecatedMQGOV_CLI_*aliases remain supported for compatibility.
v0.5.8
Changed
- BREAKING:
capabilities -o jsonschema was restructured for family alignment; domain-specific fields moved todata.domain.
v0.5.7
Added
- Global flags:
--debug,--trace,--no-color.
v0.5.6
Added
ctx export,ctx import,ctx role, andctx migrate-credentialssubcommands.audit prunesubcommand for rotated audit log cleanup.
v0.5.5
Changed
- Simplified
version -o plainandcapabilities -o plainoutput to the script-friendly family format.
v0.5.4
Changed
- Fixed release version injection by bridging main package build variables into
cmd. - Aligned root
--versionoutput with the family format by using the full CLI name.
v0.5.3
Added
- Operation commands now show their target context/backend/cluster/namespace in table/plain output and JSON data.target.
v0.5.2
Changed
- Reuse opskit-core's shared secure-backend guard for stored credentials; behavior is unchanged.
v0.5.1
RabbitMQ credential-supply fixes.
Added
ctx set --backend rabbitmq --usernameto set the RabbitMQ user with the
discrete--host/--port/--vhostflags, instead of being forced to embed it
in--amqp-url.
Fixed
MQGOV_PASSWORDis now honored at connection time when a context has no stored
credential (current context and--contextoverrides), giving a consistent
non-interactive password path. RabbitMQ AMQP and management API now use one
unified username/password: explicit--username/password (orMQGOV_PASSWORD)
overrides--amqp-urluserinfo, withguest/guestas the default.