More destination fixes for ci_check_dependency
#20274
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
octavia-squidington-iv
added
the
area/documentation
alafanechere
approved these changes
Dec 9, 2022
erohmensing
approved these changes
Dec 9, 2022
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.
Like #20110, this PR fixes even more destination docs & changelogs from #20245 (comment).
Azure Blob Storage- the readme filename needs to match the connector name.Bigquery Denormalized- we should ignore logging for docs for connectors matching-denormalized, which is a variant like-strict-encrypt.destination-jdbc- this destination was already ignored. we should ignore the doc check rather than warn that it can't be foundRedpanda-redpanda.mdwas missing the##CHANGELOGheader with which we were parsing the version