Repository navigation
Conversation
Member
Author
|
Moved the changes to local main for further discussion. |
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.
The platform installer currently uses its database owner URL both for migrations and to create Hyperdrive. That prevents installation with a company-managed Hyperdrive whose runtime role and origin differ from the owner connection. This change accepts an existing Hyperdrive ID plus its expected origin host and user, verifies the target database and disabled SQL result caching, and records the external configuration without changing or deleting it. The owner URL remains the connection for database claims, locks, and migrations.
The install guide and CLI reference describe the three new environment variables. The existing installer-managed path is unchanged.
Validation:
vp run check; 188 focused platform tests; targeted lint and formatting passed. The full suite had four failures in unrelated platform API integration tests: two 5-second timeouts and two external fetch timeouts that returned 500; rerunning the affected files with a longer timeout cleared the first two and reproduced the fetch failures.