kylon-cli 0.7.4-next.1025 → 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 +12 -19
- package/dist/kylon-bundle.manifest.json +3 -3
- package/dist/kylon-bundle.mjs +1 -1
- package/package.json +2 -2
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
|
-
|
|
644
|
-
|
|
645
|
-
|
|
646
|
-
There is intentionally no top-level `kylon secret` command.
|
|
647
|
-
|
|
648
|
-
|
|
649
|
-
|
|
650
|
-
|
|
651
|
-
|
|
652
|
-
|
|
653
|
-
|
|
654
|
-
|
|
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.
|
|
3
|
-
"fingerprint": "
|
|
4
|
-
"source_commit": "
|
|
2
|
+
"version": "0.7.4-next.1026",
|
|
3
|
+
"fingerprint": "539f1c3bb85d455db181513246a3e80703af9160272a059ecaff047550ea4dd9",
|
|
4
|
+
"source_commit": "7c198e8c2dd05a18323f253bb71a9904026fdee7"
|
|
5
5
|
}
|