STS QoS haproxy Part 1 changes : PR1 without Lua Filter - #34
Open
rohit2219 wants to merge 8 commits into
Open
Conversation
csch1n
marked this pull request as ready for review
February 27, 2026 20:40
jacquesh
requested changes
Mar 3, 2026
Author
|
testing notifications |
Author
|
@rohit2219 testing notifications |
jacquesh
approved these changes
Mar 5, 2026
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
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
Please provide a meaningful description of what this change will do, or is for.
Bonus points for including links to related issues, other PRs, or technical
references.
This is the first part of changes for extracting STS Token from haproxy. I did this for easier rollbacks in case of issues and easier PR reviews
This part of the code only attaches an attribute to the txn object where we can indicate if the transaction should be parsed or not . Currently only AssumeRole is added, but it can be used for future projects like AssumeRoleWithWebIdentity.
Note that by not including a description, you are asking reviewers to do extra
work to understand the context of this change, which may lead to your PR taking
much longer to review, or result in it not being reviewed at all.
Type of Change
✅ New Feature
Checklist