kylon-cli 0.7.4-next.1024 → 0.7.4-next.1026

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.
package/README.md CHANGED
@@ -640,25 +640,18 @@ kylon workspace connection list --toolkit custom-api-key --scope-workspace <WORK
640
640
  kylon workspace connection run --connection <CONNECTION_ID> -- curl https://api.example.com/resource
641
641
  ```
642
642
 
643
- The `kylon workspace secret` noun is retired: every verb only prints its
644
- Connection replacement, accepts no secret value, and changes nothing.
645
-
646
- There is intentionally no top-level `kylon secret` command. The namespace
647
- selects the resource and identity without inspecting unrelated local credential
648
- state:
649
-
650
- - Use `kylon workspace connection list|create|credential set|access request|run`
651
- for API-key Connections with browser authorization; the retired
652
- `kylon workspace secret` verbs only print those replacements.
653
- - Use `kylon gateway secret list|delete --agent <agent-id>` for agent-local
654
- records, authenticated by this installation's saved runtime credential
655
- through agent-scoped runtime routes. There is no `set`: a credential is
656
- stored as a Custom API Service from the agent's setup card or from
657
- Connections in Kylon, and the agent reads it from its environment.
658
-
659
- This separation prevents browser credentials from reaching the
660
- daemon-authenticated secret endpoints and avoids state-dependent command
661
- routing.
643
+ Use `kylon workspace connection list|create|credential set|access request|run`
644
+ for API-key Connections. There is no secret command any more:
645
+
646
+ - There is intentionally no top-level `kylon secret` command.
647
+ - The `kylon workspace secret` noun is retired: every verb only prints its
648
+ Connection replacement, accepts no secret value, and changes nothing.
649
+ - `kylon gateway secret` is retired too: an agent keeps no secrets of its
650
+ own, so `list`, `set` and `delete` make no request and only print the
651
+ Connection command that replaced them. A credential is stored as a Custom
652
+ API Service from the agent's setup card or from Connections in Kylon, the
653
+ agent reads it from its environment, and the person who manages the
654
+ service removes it.
662
655
 
663
656
  ```bash
664
657
  kylon auth logout --workspace <WORKSPACE_ID>
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "0.7.4-next.1024",
3
- "fingerprint": "887c645acb0e341f43400118e439f954bf0692ee192626c801b5fd00f58b4134",
4
- "source_commit": "9ead6c22781e6a54c220b51a286eda99e93135b0"
2
+ "version": "0.7.4-next.1026",
3
+ "fingerprint": "539f1c3bb85d455db181513246a3e80703af9160272a059ecaff047550ea4dd9",
4
+ "source_commit": "7c198e8c2dd05a18323f253bb71a9904026fdee7"
5
5
  }