mirror of https://github.com/agent-substrate/substrate.git synced 2026-11-11 10:23:17 +08:00

Files

T

Lior Lieberman e5a1a65084 remove non mitm dataplanes (#2015 )

Remove the plain (non-terminating) egress gateways on both dataplanes.
The "mitm" gateway, which mints a per-SNI leaf and **decides every
request by name**, is the only one, and we should stop call it mitm
gateway.

`--experimental-use-sdsmint` is also gone. 

Highly recommend review each commit at a time;

- Remove the plain agentgateway egress overlay
- Remove the plain envoy egress gateway
- Drop the gateway-variant language and the `-mitm` demos. More
specifically for the this commit: Manifest is `atenet-egress.yaml` (its
not again, the overlay and component are `agentgateway-egress`, prose
says "the egress gateway". The `-mitm` egress demos become *the* egress
demos under the plain names (the plain ones trusted only public roots
and could not do HTTPS through the gateway); e2e fixtures and the CI
deploy step follow.


> It's a good idea to open an issue first for discussion.

- [x] Tests pass
- [x] Appropriate changes to documentation are included in the PR

2026-10-01 22:50:19 +00:00

gcp-secret-manager

remove non mitm dataplanes (#2015 )

2026-10-01 22:50:19 +00:00

README.md

Add gcp secret manager as a credential provider in its own go module (#1991 )

2026-09-30 22:56:13 +00:00

README.md

Plugins

Each directory here is a self-contained plugin: a Go module of its own that plugs into substrate through its public APIs.

This is a temporary location. Each plugin will move to a repository of its own, and its path here goes away when it does. Until then:

Do not depend on these paths. Nothing else in the repository should build on, script against or link into a plugin's directory. The only references from outside a plugin are its own CI steps and pointers from the docs.
Do not import these packages. Code outside a plugin must not import it. Go already refuses most such imports, since a plugin's packages sit under its own internal/ or are main packages.
A plugin imports only substrate's public pkg/ packages, so it can move out as it is. Its go.mod replaces the substrate module with this checkout, so it builds against the current tree.