Use generator service to register AmazonS3 destination type #404
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 this PR changes/adds
This PR aims to fix the addition of AmazonS3 destination type by the generator service in the initialiaztion of the extension.
Why it does that
With the removal of sourcetypes properties from the dataplane selector logic, now the destination type must be registered during the boot and so this change allows that for the AmazonS3 type.
Further notes
Tests were added for existing class to promote quality and consistency.
Linked Issue(s)
Closes #401