Fix Finance database network resolution - #9
Merged
Conversation
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.
Summary
finlens_privatenetwork from the API servicefinlens_privatenetwork from the MCP serverfinlens_privatenetwork declarationpior_dataas the shared database networkWhy
Finance was resolving the database hostname
postgresto the legacyshared-postgrescontainer onfinlens_private(172.23.0.2) instead of the platform-managedpior-postgrescontainer onpior_data(172.24.0.2). This caused the migration to fail with PostgreSQL28P01even though thefinance_appcredentials were correct.A migration run with the database hostname temporarily overridden to
pior-postgressucceeded, confirming the network/DNS collision as the root cause.