[WIP] Implement secret manager datasource #99
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.
Implements the secret manager version datasource:
This implementation is similar to the suggested reference, however stripped down to the bare minimum (no json key decoding).
This is my first PR to this repo, so I have a few open questions:
Since I don't see many acceptance tests in the repo, I've only implemented unit tests. I'm open to implementing it if anyone can give me an example / model to follow.
Is there a way to "ignore" certain field in the doc generation? The
mock
field is not particularly useful for the enduser but mandatory (to my knowledge) to pass extra client options for unit tests.Closes #29