feat: support static connection info #648
Merged
+56
−0
Conversation
This file contains 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
enocom
force-pushed
the
static-conn-info
branch
2 times, most recently
from
cd55a6a
to
ce20bea
Compare
nancynh
approved these changes
May 15, 2024
Add support for seeding the connection info cache with static certificates and IP addresses. This is useful in development contexts and should otherwise be considered a non-production feature. With this commit, callers may now provide the path to a JSON file which contains an RSA key pair, IP addresses, and certificate chains for any number of AlloyDB instances. NOTE: the file format is subject to breaking changes. As such this feature should be considered for development only.
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.
Add support for seeding the connection info cache with static certificates and IP addresses. This is useful in development contexts and should otherwise be considered a non-production feature.
With this commit, callers may now provide the path to a JSON file which contains an RSA key pair, IP addresses, and certificate chains for any number of AlloyDB instances.
NOTE: the file format is subject to breaking changes. As such this feature should be considered for development only.