#529: Added database connection details endpoint and response and updated existing endpoint.#530
Merged
Merged
Conversation
…e and updated existing endpoint.
Contributor
Author
|
@danepowell @typhonius Can you review this ? |
danepowell
approved these changes
Apr 7, 2026
anujkaushal
approved these changes
Apr 10, 2026
Collaborator
|
@typhonius Could you please grant me access to merge PRs in this repository? @danepowell Would you be able to support my request? |
Collaborator
Agreed; @anujkaushal is the new tech lead for Acquia CLI and needs the same access as me. |
Owner
Thanks all, have invited |
Collaborator
Thanks @typhonius |
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.
This pull request introduces a new API method to retrieve database connection details for a site instance, along with a dedicated response class and corresponding tests. It also refactors the existing database response to remove connection-specific fields, ensuring a clear separation of concerns between metadata and connection information.
New functionality:
getDatabaseConnectionto theSiteInstancesendpoint, which returns database connection details for a site instance.SiteInstanceDatabaseConnectionResponse, to encapsulate database connection information such as host, username, password, and SSH host.Refactoring and cleanup:
databaseHost,databaseUserName,databasePassword) fromSiteInstanceDatabaseResponse, so it now only contains database metadata.getSiteInstanceDatabase.jsonto remove connection fields, reflecting the refactored response.getSiteInstanceDatabaseConnection.jsonfor the new connection endpoint.Testing:
getDatabaseConnectionandSiteInstanceDatabaseConnectionResponse, verifying correct parsing and field mapping. [1] [2]SiteInstanceDatabaseResponse. [1] [2]These changes improve clarity in the API by separating database metadata from connection details and provide comprehensive test coverage for the new and updated functionality.