feat: Set up config check for connection validity #14
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.
Fivetran framework expects a list of connection tests to be returned from the
ConfigurationForm
endpoint. It will then call theTest
endpoint in order for each of the tests specified.Given that the token is already a required property on the Fivetran side, for the MotherDuck destination there is only one useful check -- "can the user authenticate?". The check already existed, but it was not making use of the
TestRequest.name()
field.I thought about making an unknown test name log a warning and succeed, but this will just hide potential integration problems, so I ended up making it an error instead.
Fixes #5
For reference, here is an example of configuration tests for a Github source: