vdb-gen to handle db that have no communal auth #291
Merged
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
There are a couple of cases where a Vertica database can be created without storing authentication parms for communal: - using HDFS as the communal store - using AWS S3, but using IAM profiles for authentication vdb-gen wasn't handling this case well. For AWS S3, it was expecting to see the authentication parms. It failed when it couldn't find it. And it handles the HDFS case, but still prints out an empty credential secret when it dumps the manifests. This fixes both scenarios in vdb-gen.
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.
There are a couple of cases where a Vertica database can be created without storing authentication parms for communal:
vdb-gen wasn't handling this case well. For AWS S3, it was expecting to see the authentication parms. It failed when it couldn't find it. And it handles the HDFS case, but still prints out an empty credential secret when it dumps the manifests.
This fixes both scenarios in vdb-gen.