Feat: add test cases for Alertmanager secret config Jira receiver#8349
Merged
simonpasquier merged 2 commits intoprometheus-operator:mainfrom Feb 4, 2026
Merged
Conversation
for the missing comparison
Contributor
Author
|
@simonpasquier this is to separate the unit test implement. Pls review. |
nutmos
added a commit
to nutmos/prometheus-operator
that referenced
this pull request
Feb 14, 2026
…ometheus-operator#8349) * amcfg: add jira sanitize test cases for alertmanager secret config * amcfg: add golden file for the missing comparison
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
This PR adds test cases for sanitize methods of Jira receiver, separated from CR implement in another PR.
Relate: #7971
Type of change
What type of changes does your code introduce to the Prometheus operator? Put an
xin the box that apply.CHANGE(fix or feature that would cause existing functionality to not work as expected)FEATURE(non-breaking change which adds functionality)BUGFIX(non-breaking change which fixes an issue)ENHANCEMENT(non-breaking change which improves existing functionality)NONE(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Verification
Unit Testing
Changelog entry