stt/classic-models-agent-catalogue
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct a README that listed done work as pending

Browse Source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Stéphane Tailland
2026-08-31 14:40:49 +02:00
parent 58325b470a
commit 64fcd85b24
1 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+9 -8
View File
@@ -125,18 +125,19 @@ running library:
## Not done yet ## Not done yet
- **The Keycloak client does not exist.** `classic-models-agent-catalogue` has - The **`replicas: 1`** in `k8s/deployment.yaml` is a constraint, not a default:
to be declared in `infra-keycloak/k8s/keycloak/configmap-realm.yaml`, with conversation history lives in the process, and so does a pending write waiting
`mcp-catalog-audience` and `mcp-sales-audience` as optional scopes. Until then for approval. Moving either out is what would allow a second replica.
the exchange fails and the agent says so. - The Keycloak client is still named `classic-models-agent-catalogue` while the
- Writes, and the A2A call to Approvisionnement. Kubernetes objects say `catalog-agent`. Either is fine — pick one.
- Deployment manifests — they belong in `classic-models-agent-platform` once a
second agent shows what is actually shared. Everything this section used to list is done: the Keycloak client exists, writes
and the A2A call to the supply agent work, and `k8s/` deploys through Flux.
## Deployment ## Deployment
``` ```
gitea.sttlab.eu/stt/classic-models-agent-catalogue:v0.1.0 gitea.sttlab.eu/stt/classic-models-agent-catalogue:v0.3.2
``` ```
gitea's own registry rather than ghcr, so the image sits beside the source it gitea's own registry rather than ghcr, so the image sits beside the source it