Follow the supply agent's rename
Its Keycloak client and audience scope changed name; the peer entry and the environment variables that point at it move with them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -91,7 +91,7 @@ for that reason; in the cluster the names resolve instantly.
|
||||
## Deployment
|
||||
|
||||
```
|
||||
gitea.sttlab.eu/stt/classic-models-agent-assistant:v0.2.1
|
||||
gitea.sttlab.eu/stt/classic-models-agent-assistant:v0.3.0
|
||||
```
|
||||
|
||||
`k8s/` is what runs, `dev/` is the Flux plumbing. Two manual applies close the
|
||||
|
||||
+1
-1
@@ -29,4 +29,4 @@ data:
|
||||
# specialists.py. Set here so the rename took effect without rebuilding an
|
||||
# image; the defaults in the code carry the same values for the next build.
|
||||
ASSISTANT_URL_CATALOGUE: http://catalog-agent.agents.svc.cluster.local:8080/
|
||||
ASSISTANT_URL_APPROVISIONNEMENT: http://supply-agent.agents.svc.cluster.local:8080/
|
||||
ASSISTANT_URL_SUPPLY: http://supply-agent.agents.svc.cluster.local:8080/
|
||||
|
||||
+1
-1
@@ -28,7 +28,7 @@ spec:
|
||||
# gitea's own registry: the image sits beside the source it was built
|
||||
# from and inherits the repo's public visibility, so the pull needs no
|
||||
# credentials at all.
|
||||
image: gitea.sttlab.eu/stt/classic-models-agent-assistant:v0.2.1
|
||||
image: gitea.sttlab.eu/stt/classic-models-agent-assistant:v0.3.0
|
||||
ports:
|
||||
- name: http
|
||||
containerPort: 8080
|
||||
|
||||
@@ -50,10 +50,10 @@ CATALOGUE = Specialist(
|
||||
)
|
||||
|
||||
|
||||
APPROVISIONNEMENT = Specialist(
|
||||
name="approvisionnement",
|
||||
SUPPLY = Specialist(
|
||||
name="supply",
|
||||
url="http://supply-agent.agents.svc.cluster.local:8080/",
|
||||
audience_scope="classic-models-agent-approvisionnement-audience",
|
||||
audience_scope="classic-models-agent-supply-audience",
|
||||
serves="supply: whether a reference can be promised, from stock on hand",
|
||||
decides=(
|
||||
"whether a product can be promised to a customer, and why not when it cannot",
|
||||
@@ -69,7 +69,7 @@ APPROVISIONNEMENT = Specialist(
|
||||
#: Note what these two have in common from here: nothing. One is PydanticAI over
|
||||
#: MCP, the other n8n behind an adapter. The orchestrator cannot tell, and that
|
||||
#: is the point of the protocol.
|
||||
SPECIALISTS: tuple[Specialist, ...] = (CATALOGUE, APPROVISIONNEMENT)
|
||||
SPECIALISTS: tuple[Specialist, ...] = (CATALOGUE, SUPPLY)
|
||||
|
||||
|
||||
def by_name(name: str) -> Specialist | None:
|
||||
|
||||
Reference in New Issue
Block a user