-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Add "salt" beacon #56575
Add "salt" beacon #56575
Conversation
40d3466
to
15e8cea
Compare
Did anyone get a chance to look at this PR? |
fba7479
to
3562690
Compare
@twangboy I fixed the failing tests. Can this PR be reviewed, please ? |
3562690
to
5666957
Compare
@twangboy bump |
8b80454
to
e13b35c
Compare
pr suggestions
e13b35c
to
79432a6
Compare
@xeacott Does your approval mean this will go into Aluminum? Sorry to bug ya, but I'm just curious and wanted to make sure this gets included before it becomes too out of date with master. |
@jtraub91 Unfortunately no; we have a traditional ruling in the Core team that most PR's require 3 approvals to be considered "done done" by us. I will kindly ping @sagetherage as she can provide a much better answer about this getting Aluminum. |
Since @s0undt3ch requested changed I will ask for his re-review and I have updated this with master so it is running tests again, then likely it can be merged, these labels will also help :) |
how many reviewers? well, if tests are passing and tests written, docs, and changelog then only 1 review is needed, but we do like review from those that have requested changes, and 3 approvals is mandatory for anything that doesn't have all of those - clearer? Maybe, I have labeled so Megan can review for merge. |
13fa412
Apparently, the indentation after the beacons:
salt_monitor:
- salt_fun:
- slsutil.renderer:
args:
- salt://states/apache.sls
kwargs:
- default_renderer: jinja
- test.ping
- interval: 3600 # seconds |
@max-arnold yes good catch that was a typo in the docstring! 😳 |
What does this PR do?
Adds new beacon:
salt_monitor
What issues does this PR fix or reference?
Closes #56461
New Behavior
Allows user to specify one or more salt function (optionally with args / kwargs) to execute every beacon interval. The beacon will fire an event only if the return from its function is "truthy" and the event will include the function call (with args / kwargs, if applicable), as well as the return data.
Tests written?
Yes
Commits signed with GPG?
No