integration/kusto: add basic integration test for kusto output plugin #66
Conversation
This file contains hidden or 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
Signed-off-by: Gershon Papiashvili <[email protected]>
4 tasks
|
Thanks for this @papigers , looks good to me. Only thing I'd say is can you add a license to the dependency you created just so we're covered? |
|
@niedbalski only issue I can really see is handling runs without the new plugin, for the mainline branch and any PRs based on it currently. |
|
@patrick-stephens added license now |
|
Ah, that issue with packer is down to coming from a fork so can be ignored here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Integration test for the new Kusto output plugin (fluent/fluent-bit#5645).
The deployment uses this reverse proxy I created that authenticates using microsoft's authentication library https://github.com/papigers/msal-proxy (only to not implement whole authentication flow in Bash, hope that's fine).
Before merging, an azure cluster needs to be created and pre-configured (database, ingestion mapping, etc...)