-
Notifications
You must be signed in to change notification settings - Fork 20
[ADMINAPI-1416] Switch to Docker Hardened Image for PostgreSQL #415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
70b5813
[AC-582] Switch to Docker Hardened Image for PostgreSQL
jpardogrowthaccelerationpartners f29109d
Solve docker analysis errors and nginx vulnerabilities
jpardogrowthaccelerationpartners d949123
Solve docker build publish analysis and bruno claimsets order test
jpardogrowthaccelerationpartners f077131
Solve docker build package version and bruno claimsets order tests
jpardogrowthaccelerationpartners b69bc7b
Solve bruno Application by Ids test
jpardogrowthaccelerationpartners c957513
Adding suppressions for the two false positive reports
jpardogrowthaccelerationpartners 6e31262
Solving comments
jpardogrowthaccelerationpartners 09ee49c
Update sha256 on docker images
jpardogrowthaccelerationpartners 08dffdd
Change alpine:3.20 with the latest packages
jpardogrowthaccelerationpartners 679b43e
Use the zip version allowed on Alpine3.20
jpardogrowthaccelerationpartners 36c36e4
Update alpine version and solve comment of claude
jpardogrowthaccelerationpartners a0880f4
Fix comments
jpardogrowthaccelerationpartners File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we move all of these Bruno script changes to a separate PR, instead of mixing them in with the base image hardening?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thinking about it, I think it's better to leave it here because if I put them in another PR we wouldn't be able to merge this one since the test check wouldn't pass.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please explain: I do not understand why changes to the Docker images caused changes to Bruno scripts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stephenfuqua These Bruno changes are not “script plumbing” changes; they are assertion-hardening updates needed because the Docker hardening changed runtime behavior in ways that exposed overly strict test assumptions.
Specifically:
The GET Applications by IDs tests previously assumed exactly 2 results.
We updated them to validate the API contract correctly: returned records must be a subset of requested IDs.
The ClaimSets sorting tests previously assumed one exact comparator/collation path (lodash orderBy equality).
With the updated image stack, sort behavior can differ by locale/collation details while still being valid ascending order, so we now assert valid ascending order (ordinal or case-insensitive), not one brittle implementation ordering.
Why this was not needed before:
The previous image/runtime combination happened to satisfy those stricter assumptions.
After base-image hardening (Postgres/Alpine/runtime path changes), those assumptions became flaky/invalid even though API behavior remained contract-correct.
So these Bruno updates are required to keep E2E tests aligned with API contract semantics under the hardened images, not to introduce unrelated test behavior.