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.

Hans Hasselberg e26ac3f388 Update HCP bootstrapping to support existing clusters 1.14.x version (#17303) ... * Persist HCP management token from server config We want to move away from injecting an initial management token into Consul clusters linked to HCP. The reasoning is that by using a separate class of token we can have more flexibility in terms of allowing HCP's token to co-exist with the user's management token. Down the line we can also more easily adjust the permissions attached to HCP's token to limit it's scope. With these changes, the cloud management token is like the initial management token in that iit has the same global management policy and if it is created it effectively bootstraps the ACL system. * Update SDK and mock HCP server The HCP management token will now be sent in a special field rather than as Consul's "initial management" token configuration. This commit also updates the mock HCP server to more accurately reflect the behavior of the CCM backend. * Refactor HCP bootstrapping logic and add tests We want to allow users to link Consul clusters that already exist to HCP. Existing clusters need care when bootstrapped by HCP, since we do not want to do things like change ACL/TLS settings for a running cluster. Additional changes: * Deconstruct MaybeBootstrap so that it can be tested. The HCP Go SDK requires HTTPS to fetch a token from the Auth URL, even if the backend server is mocked. By pulling the hcp.Client creation out we can modify its TLS configuration in tests while keeping the secure behavior in production code. * Add light validation for data received/loaded. * Sanitize initial_management token from received config, since HCP will only ever use the CloudConfig.MangementToken. * Add changelog entry * pin logr * pin stdr --------- Co-authored-by: freddygv <freddy@hashicorp.com> Co-authored-by: John Murret <john.murret@hashicorp.com>		2 years ago
..
acl	Backport of Update go version to 1.19 into release/1.14.x (#15139)	2 years ago
agent	Update HCP bootstrapping to support existing clusters 1.14.x version (#17303)	2 years ago
catalog	…
cli	…
config	feat(cli): enable to delete config entry from an input file (#13677)	2 years ago
connect	command: Fix logger not initializing properly in envoy command (#16148) (#16153)	2 years ago
debug	Backport of Allow consul debug on non-ACL consul servers into release/1.14.x (#15167)	2 years ago
event	…
exec	…
flags	Support auth method with snapshot agent [ENT] (#15020)	2 years ago
forceleave	…
helpers	Add support for configuring Envoys route idle_timeout (#14340) (#15611)	2 years ago
info	…
intention	…
join	…
keygen	…
keyring	…
kv	Fix Consul KV CLI 'GET' flags 'keys' and 'recurse' to be set together (#13493)	2 years ago
leave	…
lock	…
login	Extract AWS auth implementation out of Consul (#13760)	2 years ago
logout	…
maint	…
members	Manual Backport of [OSS] security: update go to 1.20.1 into release/1.14.x (#16321)	2 years ago
monitor	…
operator	…
peering	Backport of Bring back parameter ServerExternalAddresses in GenerateToken endpoint into release/1.14.x (#15296)	2 years ago
reload	…
rtt	…
services	fix(cli): error message in service deregister subcommand (#14028)	2 years ago
snapshot	…
tls	Backport of Update go version to 1.19 into release/1.14.x (#15139)	2 years ago
validate	…
version	Fix issue with consul version tests	3 years ago
watch	…
registry.go	feat(cli): add initial peering cli commands	2 years ago
registry_oss.go	Add build tag for oss (#13279)	3 years ago