-
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
feat(exit-code): configure exit code on warning #2
Conversation
3d9a88f
to
3cffd38
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #2 +/- ##
==============================================
- Coverage 97.61% 84.11% -13.51%
- Complexity 100 109 +9
==============================================
Files 18 19 +1
Lines 294 384 +90
==============================================
+ Hits 287 323 +36
- Misses 7 61 +54
☔ View full report in Codecov by Sentry. |
3cffd38
to
f6e0456
Compare
f6e0456
to
150ac42
Compare
@xarem these checks are getting out of hand ... |
@tuxes3 in case of a warning, the http response code for the HTTP check is still 503. How about making it configurable like this? whatwedo_monitor:
endpoint:
api:
http_status_code:
warning: 503
critical: 503
command:
exit_code:
warning: 1
critical: 1 In addition, please update the docs with the change. |
@xarem ready for second review |
Furthermore i removed all deprecations and made the bundle only usable starting symfony
6.3
.That would mean we need to tag the next version
v2.0.0
.Issue: #1