baf886c6f3
The gist here is that now we use a value-type struct proxycfg.UpstreamID as the map key in ConfigSnapshot maps where we used to use "upstream id-ish" strings. These are internal only and used just for bidirectional trips through the agent cache keyspace (like the discovery chain target struct). For the few places where the upstream id needs to be projected into xDS, that's what (proxycfg.UpstreamID).EnvoyID() is for. This lets us ALWAYS inject the partition and namespace into these things without making stuff like the golden testdata diverge. |
||
|---|---|---|
| .. | ||
| connect_proxy.go | ||
| ingress_gateway.go | ||
| manager.go | ||
| manager_test.go | ||
| mesh_gateway.go | ||
| mesh_gateway_oss.go | ||
| naming.go | ||
| naming_oss.go | ||
| naming_test.go | ||
| proxycfg.go | ||
| snapshot.go | ||
| state.go | ||
| state_test.go | ||
| terminating_gateway.go | ||
| testing.go | ||
| upstreams.go | ||