-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[SHOT-97] fix: target container names instead of bare service hostnames #7894
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
Draft
mimartin12
wants to merge
4
commits into
main
Choose a base branch
from
fix/SHOT-97-nginx-proxy-hostname-collision
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+25
β19
Draft
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
87b1830
[SHOT-97] fix: target container names instead of bare service hostnames
mimartin12 0fb9440
Pin remaining internal service URIs to container names
mimartin12 35bec05
Merge branch 'main' into fix/SHOT-97-nginx-proxy-hostname-collision
mimartin12 f05fadd
Remove inert internalScim override
mimartin12 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
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.
β QUESTION: Are the other internal service URIs intentionally left on bare service names?
Details
This pins
internalIdentitytohttp://bitwarden-identity:5000, but the other internal URIs still fall through toBuildInternalUri's default, which produces bare service names (http://identity:5000style). For example,InternalNotificationsresolves tohttp://notifications:5000and is actively consumed byNotificationsApiPushEngine(src/Core/Platform/Push/Engines/NotificationsApiPushEngine.cs:28), so it shares the exact same cross-container hostname-collision failure mode this PR is fixing for identity.If SHOT-97 is scoped only to auth traffic that's fine β just confirming whether
InternalNotifications/InternalApi/InternalVault/InternalSso(and the mssqlDataSource = "tcp:mssql,1433"at line 71) were deliberately left out of this change.