-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore: remove need for extract_alerts.sh #1
chore: remove need for extract_alerts.sh #1
Conversation
@@ -62,6 +62,3 @@ local.mk | |||
|
|||
# Ignore temporary files created by the Makefile | |||
*.mktmp.* | |||
|
|||
#Ignore temporary alert yaml files created by the Makefile | |||
*_alerts.yaml |
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.
@grdryn This I think is needed. Not only for these changes but so that anyone running prometheus-alert tests locally doesn't push these files by mistake.
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.
Ahh, I see you've added a separate .gitignore. But I'm not sure if there is a benefit of having a separate file for this.
2d87196
to
b4195fd
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.
LGTM
Make excels at tracking generated output files from specified input files (it might be the only thing it's good at). By having a convention of naming the generated rule files and their corresponding unit test files based on the file names in the ConfigMap, then we don't need a separate script to track the difference in what the files are called inside and outside the ConfigMap, which would need to be updated each time a new unit test file is added. With this change, as long as you name your unit test file in the appropriate way, and there's a corresponding entry in the ConfigMap, then the rule file should get extracted in the expected way.
b4195fd
to
e8509c9
Compare
Current implementation incorrectly calls removal of a header which is manifested in ingress gateway proxy logs: ``` envoy lua external/envoy/source/extensions/filters/http/lua/lua_filter.cc:930 script log: [string "function envoy_on_request(request_handle)..."]:10: bad argument #1 to 'remove' (N5Envoy10Extensions11HttpFilters3Lua16HeaderMapWrapperE expected, got string` ``` This fixes the Lua syntax and marks Service Mesh Features related to KServe setup as `Managed()`. This ensures that updating the existing filters will happen on operator upgrade or next reconcile.
…ting (#1…" (red-hat-data-services#1122) This reverts commit d2f656a.
Make excels at tracking generated output files from specified input files (it might be the only thing it's good at).
By having a convention of naming the generated rule files and their corresponding unit test files based on the file names in the ConfigMap, then we don't need a separate script to track the difference in what the files are called inside and outside the ConfigMap, which would need to be updated each time a new unit test file is added. With this change, as long as you name your unit test file in the appropriate way, and there's a corresponding entry in the ConfigMap, then the rule file should get extracted in the expected way.
Description
How Has This Been Tested?
make test-alerts
make test-alerts
againmake -B test-alerts
-B
Screenshot or short clip
Merge criteria