[CIVIS-9333] support custom configuration tags supplied from the environment #166
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 does this PR do?
There are some configurations that cannot be directly identified and reported automatically. For those cases, the user must provide the configuration details to the library so CI Visibility can properly identify them. These tags affect the test fingerprint. These custom configurations are passed via DD_TAGS with a test.configuration. prefix, that is, every test.configuration.* tag will be treated as a custom configuration.
We send these custom configurations when requesting library settings and skippable tests in
data.attributes.configurations.custom field
.How to test the change?
Using anmarchenko/sidekiq
Test with custom configurations:
Logs when sending skippable request:
Logs when sending settings request: