DX-90 Flakeguard: include codeowners test path and failed test log url in splunk #1671
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.





Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes enhance the functionality of the flakeguard tool by removing redundant Splunk integration directly in the aggregation command, which simplifies the codebase. Moreover, it introduces modular commands for interacting with GitHub and Splunk, allowing more flexible and focused operations. Importantly, it maps test results to specific paths and code owners, providing more detailed and actionable insights for test failures.
What
splunk-url,splunk-token,splunk-event) from theAggregateResultsCmdflags.WithRepoPathandWithCodeOwnersPathoptions to include repository path and CODEOWNERS file path in the aggregation process.GetGHArtifactLinkCmdfor fetching GitHub artifact links, encapsulating this functionality and making it reusable.SendToSplunkCmdcommand for sending test reports to Splunk, isolating this functionality into its own operation.generate-reportcommand to use afailedLogsURLfor linking to failed test logs instead of fetching artifact links directly, simplifying its process.example_test_packageto reflect new mappings to test paths and code owners, providing more detailed information on test failures.