FOSSA-TEST #3
Draft
FOSSA-TEST #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* docs: clarify LTS language
hashicorp#20876) Currently, when a client starts a blocking query and an ACL token expires within that time, Consul will return ACL not found error with a 403 status code. However, sometimes if an ACL token is invalidated at the same time as the query's deadline is reached, Consul will instead return an empty response with a 200 status code. This is because of the events being executed. 1. Client issues a blocking query request with timeout `t`. 2. ACL is deleted. 3. Server detects a change in ACLs and force closes the gRPC stream. 4. Client resubscribes with the same token and resets its state (view). 5. Client sees "ACL not found" error. If ACL is deleted before step 4, the client is unaware that the stream was closed due to an ACL error and will return an empty view (from the reset state) with the 200 status code. To fix this problem, we introduce another state to the subsciption to indicate when a change to ACLs has occured. If the server sees that there was an error due to ACL change, it will re-authenticate the request and return an error if the token is no longer valid. Fixes hashicorp#20790
* feat(v2dns): enable v2 dns as default * changelog
hashicorp#20844) * Adds docs to upgrade-specific page to include the removal of the deprecated API Gateway stanza for 1.19 * Apply suggestions from code review Co-authored-by: Jared Kirschner <[email protected]> * Remove legacy api-gateway from helm docs * change .Values.apiGateway to .apiGateway --------- Co-authored-by: Jared Kirschner <[email protected]>
Per https://osv.dev/vulnerability/GO-2024-2631 this vulnerability is not present in the version currently used (go-jose/[email protected]).
* update changelog for 1.18.1 * update changelog
* Update Dockerfile: bump alpine * Create 20897 * Rename 20897 to 20897.txt
Update Dockerfile
…l server (hashicorp#20926) * put conditionals are hcp initialization for consul server * put more things behind configuration flags * add changelog * TestServer_hcpManager * fix TestAgent_scadaProvider
Signed-off-by: availhang <[email protected]>
Update python SDKs The original python-consul is unmaintained with no activity for 6 years. The python-consul2 fork has had no activity for 3 years, whether it's commits or responding to PRs and issues.
…chable from peered cluster (hashicorp#19881) * Include SNI + root PEMs from peered cluster on terminating gw filter chain This allows an external service registered on a terminating gateway to be exported to and reachable from a peered cluster * Abstract existing logic into re-usable function * Regenerate golden files w/ new listener logic * Add changelog entry * Use peering bundles that are stable across test runs
remove registation of api gateway controller
Add diagrams about write flow through Raft
* Bump go version * Bump x/net * Bump envoy version * Add changelog --------- Co-authored-by: Michael Zalimeni <[email protected]>
* update go-control-plane envoy dependency to 0.12.0 * add changelog * go mod tidy * fix linting issues * add agent/grpc-internal to the list of SA1019 ignores
…orp#20977) This operation would previously fail due to unconsumed bytes in the decoder buffer when reading the Ent snapshot (the first byte of the record would be misinterpreted as a type indicator, and the remaining bytes would fail to be deserialized or read as invalid data). Ensure restore succeeds by decoding the ignored record as an interface{}, which will consume the record bytes without requiring a concrete target struct, then moving on to the next record.
docs: Fix wrong indentation of `to` block in cross-namespace `backendRef` example YAML file
…ashicorp#20873) * Define file-system-certificate config entry * Collect file-system-certificate(s) referenced by api-gateway onto snapshot * Add file-system-certificate to config entry kind allow lists * Remove inapplicable validation This validation makes sense for inline certificates since Consul server is holding the certificate; however, for file system certificates, Consul server never actually sees the certificate. * Support file-system-certificate as source for listener TLS certificate * Add more required mappings for the new config entry type * Construct proper TLS context based on certificate kind * Add support or SDS in xdscommon * Remove unused param * Adds back verification of certs for inline-certificates * Undo tangential changes to TLS config consumption * Remove stray curly braces * Undo some more tangential changes * Improve function name for generating API gateway secrets * Add changelog entry * Update .changelog/20873.txt Co-authored-by: Jared Kirschner <[email protected]> * Add some nil-checking, remove outdated TODO * Update test assertions to include file-system-certificate * Add documentation for file-system-certificate config entry Add new doc to nav * Fix grammar mistake * Rename watchmaps, remove outdated TODO --------- Co-authored-by: Melisa Griffin <[email protected]> Co-authored-by: Jared Kirschner <[email protected]>
* add upstream limits to mesh gateway cluster generation * changelog * go mod tidy * readd changelog data * undo reversion from rebase * run codegen * Update .changelog/20945.txt Co-authored-by: Nathan Coleman <[email protected]> * address notes * gofmt * clean up * gofmt * Update agent/proxycfg/mesh_gateway.go * gofmt * nil check --------- Co-authored-by: Nathan Coleman <[email protected]>
As of Docker Engine 26.0.0 (moby/moby#47062), IPv6 is enabled by default where supported. This causes issues for our tests attempting to resolve requests to other containers over localhost, since on Linux IPv6 will be preferred over IPv4 when available when applying the default behavior defined in RFC3484. As a workaround, force IPv4 with a flag passed to `docker run`.
…e/1.20.x (hashicorp#21865) backport of commit 5934d8b Co-authored-by: Michael Zalimeni <[email protected]>
…and L7 headers feature availability into release/1.20.x (hashicorp#21880) backport of commit a44b262 Co-authored-by: Michael Zalimeni <[email protected]>
…h hostnames into release/1.20.x (hashicorp#21882) * backport of commit a80ee72 * backport of commit f270ab5 --------- Co-authored-by: Tom Davies <[email protected]>
…ashicorp#21885) backport of commit 27774d7 Co-authored-by: boruszak <[email protected]>
…hashicorp#21322) * backport of commit 6bb87a6 * backport of commit 62066fd * backport of commit d05c844 * backport of commit fedb242 --------- Co-authored-by: boruszak <[email protected]>
* docs: v1.19 corrections (hashicorp#21324) * release notes * Usage pages fixes * empty commit
* Update CHANGELOG.md * Update VERSION
…from the snapshot
sarah-oloumi
force-pushed
the
platform/fossa
branch
from
b8310e0 to
0cb078f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Testing & Reproduction steps
Links
PR Checklist