Read the connection URI from the environment. #325
Merged
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.
What
The connection URI can now be provided from the environment, using
"uri": {"variable": "..."}
.This means that we can use the same configuration in development and production, and enables the CLI or Cloud build infrastructure to fill it in with e.g. a region-specific URL.
How
We replace the
ResolvedSecret
from the NDC SDK (which has also been removed from the SDK) with our ownSecret
type, which can bePlain
orFromEnvironment
. We then handle the case appropriately, whereas before, we would panic if we ever received a non-resolved secret.I have introduced the
Environment
trait to supply environment variables. During normal execution, this is a wrapper aroundsys::env::var
. In tests, however, we can useEmptyEnvironment
, or aHashMap
containing test data.This also simplified a couple of pieces of test infrastructure.
ndc-postgres-cli update
.