Skip to content
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.

SEP 30: Event Driven State Enforcer #40

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions 0030-add_beacons_from_states.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
- Feature Name: Add Beacons from Salt States
- Start Date: 2020-12-21
- SEP Status: Draft
- SEP PR: (leave this empty)
- Salt Issue: (leave this empty)

# Summary
[summary]: #summary

Adding a new global option to Salt state system that would audomatically add a beacon on the targeted minion for specific functions in specific state modules.

# Motivation
[motivation]: #motivation

Adding this new option would allow beacons easier and associating them with Salt managed resources.

# Design
[design]: #detailed-design

The design and implementation of this new option would done in a similar way to the mod_watch system. During a state run
the various individual states will be scanned and those that include the beacon option will be run through a function that
calls a "mod_beacon" function in the desired state module. This "mod_beacon" function would create the beacon using the
configured resources associated with the state in question, eg. the PKGs, files, or services.

## Alternatives
[alternatives]: #alternatives

N/A

## Unresolved questions
[unresolved]: #unresolved-questions

- If we want to allow the configured beacon to be configurable or only have specific states use specific beacons.
- Allow the beacons for specific use cases to be combined, eg. a common beacon which monitors PKGs.

# Drawbacks
[drawbacks]: #drawbacks

Why should we *not* do this? Please consider:

- This addition would add another level of complexity to the state system.