-
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
Pass grains in minion startup event #54948
Pass grains in minion startup event #54948
Conversation
772336e
to
581a0e0
Compare
…nfiguration parameter
581a0e0
to
198d7f6
Compare
@saltstack/core-pr-reviewers Could you please take a look here? Seems like the tests aren't running. |
Any update here, please. |
@saltstack/core-pr-reviewers @DmitryKuzmenko this is now waiting since October, could you have a look in the near future by any chance? |
Hey @s0undt3ch, thanks for taking a look here. Tests are looking good! |
I just discovered that this feature (when enabled) will append grains to other events sent from a minion (not just the start event): Both commands
result in the following master event:
|
@max-arnold just passing through on this PR - was that a suggestion that we should create a new PR to update this behavior? If so, would you mind opening an issue so it doesn't get lost here in the PR? Otherwise feel free to ignore this comment 🙂 |
Note
The previous PR against develop branch #54087 has more discussion about the background for this change.
What does this PR do?
Adds a configuration option to have a selection of grains in the minion start event.
Reason behind this is better integration with Uyuni, especially when a lot of minions are starting in a short time frame - we need to get some minimal data (at least the
machine_id
) and getting it separately as a reaction to the minion start event (via a separate call or a startup state) generates considerable load on the master.By default, there will be no grains passed to the event.
Previous Behavior
New Behavior
Tests written?
Yes
Commits signed with GPG?
No