Deploy using complete_punch_32G configuration and run check-platform.sh.
Default : Elastalert send success for archiving and housekeeping
Without starting apache_httpd : Elastalert send success for housekeeping and failure for archiving
Without starting admin : Elastalert send success for archiving and failure for housekeeping
Author's checklist (You)
Before submitting merge request:
[x] Resolve existing conflicts with a merge from the targeted branch into yours
[x] Proceed to the tests
[x] Check that the documentation explains these changes
[x] Assign and inform a reviewer
After success review :
[ ] Push your branch
Reviewer's checklist (Reviewer)
[ ] Technical review with the author
[ ] Proceed to the tests
[ ] Check that the documentation explains these changes
[ ] Review and tests are done
[ ] Inform the autor that the rieview is validated. The autor must be the one to merge its branch into the targeted one and push
Related Issue
https://gitlab.thalesdigital.io/punch/product/pp-punch/-/issues/803
How was it tested ?
Deploy using complete_punch_32G configuration and run check-platform.sh.
Default : Elastalert send success for archiving and housekeeping Without starting apache_httpd : Elastalert send success for housekeeping and failure for archiving Without starting admin : Elastalert send success for archiving and failure for housekeeping
Author's checklist (You)
Reviewer's checklist (Reviewer)