Implement hash based routing test#1911
Merged
Merged
Conversation
1 task
hoffmaen
reviewed
Apr 14, 2026
hoffmaen
reviewed
Apr 14, 2026
hoffmaen
reviewed
Apr 15, 2026
hoffmaen
approved these changes
Apr 15, 2026
Contributor
|
So this new test requires cf-deployment >= v55.2.0, correct? Then we should cut a new CATs release with according release notes. |
Contributor
Author
|
@jochenehret, yes. |
jochenehret
approved these changes
Apr 16, 2026
jochenehret
left a comment
jochenehret
left a comment
Contributor
There was a problem hiding this comment.
Tested with capi-release 1.231.0 and routing-release 0.374.0, works.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Are you submitting this PR against the develop branch?
Yes
What is this change about?
Hash-based routing discussed in the RFC0042 has been recently released with cf-deployment v55.2.0
The current PR extends the existing tests for the per-route options and provides implementations for a new acceptance test to ensure the hash-based routing works e2e as expected.
Please provide contextual information.
What version of cf-deployment have you run this cf-acceptance-test change against?
cf-deployment v55.4.0
Please check all that apply for this PR:
Did you update the README as appropriate for this change?
If you are introducing a new acceptance test, what is your rationale for including it CATs rather than your own acceptance test suite?
CATs should validate common operator workflows.
CATs is not a regression test suite.
CATs is run by every component team to validate their releases before promotion.
How many more (or fewer) seconds of runtime will this change introduce to CATs?
N/A
What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!
@hoffmaen