You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

hc-github-team-consul-core 2b4d96a45e Backport of testing/deployer: update deployer to use v2 catalog constructs when requested into release/1.17.x (#19492) ... testing/deployer: update deployer to use v2 catalog constructs when requested (#19046) This updates the testing/deployer (aka "topology test") framework to conditionally configure and launch catalog constructs using v2 resources. This is controlled via a Version field on the Node construct in a topology.Config. This only functions for a dataplane type and has other restrictions that match the rest of v2 (no peering, no wanfed, no mesh gateways). Like config entries, you can statically provide a set of initial resources to be synced when bringing up the cluster (beyond those that are generated for you such as workloads, services, etc). If you want to author a test that can be freely converted between v1 and v2 then that is possible. If you switch to the multi-port definition on a topology.Service (aka "workload/instance") then that makes v1 ineligible. This also adds a starter set of "on every PR" integration tests for single and multiport under test-integ/catalogv2 Co-authored-by: R.B. Boyer <4903+rboyer@users.noreply.github.com>		1 year ago
..
internal/ipamutils	…
consul.go	Backport of testing/deployer: update deployer to use v2 catalog constructs when requested into release/1.17.x (#19492)	1 year ago
files.go	…
net.go	…
v2.go	Backport of testing/deployer: update deployer to use v2 catalog constructs when requested into release/1.17.x (#19492)	1 year ago
v2_decode.go	Backport of testing/deployer: update deployer to use v2 catalog constructs when requested into release/1.17.x (#19492)	1 year ago