@klok-integration/cli 0.7.297 → 0.7.300

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/assets/agents/skills/klok-cli/reference.md +3 -2
  2. package/dist/cli.js +7 -7
  3. package/package.json +1 -1
package/assets/agents/skills/klok-cli/reference.md CHANGED
@@ -908,8 +908,9 @@ services: package-lock.json, uv.lock, poetry.lock or the requirements at the dep
908
908
 
909
909
  --broker reads the superuser client from Vault (secret/klok/environment/pulsar/klok-broker) with your own Vault
910
910
  token (VAULT_TOKEN or ~/.vault-token from `vault login`; in CI the job's login), trusts the Klok Root CA from
911
- Vault's pki/ca/pem, and only reads. Vault's own certificate is self-signed: set VAULT_CACERT (as for the vault CLI)
912
- or NODE_EXTRA_CA_CERTS. KLOK_PULSAR_TOKEN and KLOK_PULSAR_CA_FILE replace the Vault reads when you have them.
911
+ Vault's pki/ca/pem, and only reads. Vault's own certificate is from Let's Encrypt, which Node trusts; VAULT_CACERT and
912
+ NODE_EXTRA_CA_CERTS are still added when set. KLOK_PULSAR_TOKEN and KLOK_PULSAR_CA_FILE replace the Vault reads when
913
+ you have them.
913
914
 
914
915
  Broker client versions: Java integrations do not declare the broker client; it comes with the Quarkus extension.
915
916
  The version shown is the resolved one: the classpath the build's documentation scan prints in the build log