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
Fixed Monitoring Integration Tests #4699
Fixed Monitoring Integration Tests #4699
Conversation
14267a7
to
1a225ab
Compare
/retest |
1a225ab
to
7960eb6
Compare
@@ -69,16 +69,36 @@ export const saveAsDefault = firstElementByTestID('save-as-default'); | |||
|
|||
export const defaultAlertmanagerYaml = Base64.encode(`"global": | |||
"resolve_timeout": "5m" | |||
"inhibit_rules": |
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.
OK as a follow on, but we should read the initial config from the cluster instead of hard-coding here. We do this for the OAuth scenario:
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.
Ok, but I believe the initial alertmanager conifg gets overwritten after updating the alertmanager Secret.
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.
Ok, but I believe the initial alertmanager conifg gets overwritten after updating the alertmanager Secret.
beforeAll
will read it before any tests are run
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.
I believe once you update the alert-main Secret with an updated alertmanager.yaml it overwrites the initial alertmanager config. I'm not sure there is a way to get what the original was.
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.
Right, that's why you read the initial config before updating the secret :)
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.
ah, read and save and restore on beforeAll
-got it :-)
d180f27
to
f52bb48
Compare
@spadgett Fixed monitoring and alertmanager integration tests |
f52bb48
to
0432846
Compare
0432846
to
a6c13e7
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.
/approve
/lgtm
thanks @dtaylor113 👍
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dtaylor113, spadgett The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
Updated monitoring and alertmanager integration suits to only work with test Receivers created in the tests.