-
Notifications
You must be signed in to change notification settings - Fork 3.8k
feat: integrate all supported rocketchat attributes for alertmanagerconfig CR #8016
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
I can't see how the failing e2e tests are related to this PR |
|
Anything else that is missing or should be changed? |
|
@simonpasquier as requested I have dropped the file attributes even that I still don't get why these attributes are fine for other providers than Rocket.Chat. |
94d937e to
5a54a7b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @tboerger could you just rebase and re-run make--always-make format generate, since the docs check is failing. Other than that lgtm. Thanks
5a54a7b to
177e1a8
Compare
|
@heliapb just did that and pushed the fix. |
|
@simonpasquier anything else you want to have changed? Or are we ready to go for it? :) |
Description
Currently the AlertmanagerConfig resource does not map all required fileds into the Alertmanager, with this change all currently supported attributes should be added.
I have no idea if it is OK to change this on both API versions, if there is something obviously wrong for you please tell me, it's my first contribution to this project.
Closes: #8009
Closes: #8008
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
Please check the Prometheus-Operator testing guidelines for recommendations about automated tests.
Added basic unit test.
Changelog entry
Please put a one-line changelog entry below. This will be copied to the changelog file during the release process.