mirror of
https://github.com/Security-Onion-Solutions/securityonion.git
synced 2026-05-10 13:20:30 +02:00
Mike Reeves
72105f1f2f
New minions run highstate as part of onboarding, which already applies the telegraf state with the fresh pillar entry we just wrote. Pushing telegraf a second time from the reactor is redundant. - Remove the MINION-scoped salt.state block from the orch; keep only the manager-side postgres.auth + postgres.telegraf_users provisioning. - Stop passing minion_id as pillar in the reactor; the orch doesn't reference it anymore.
17 lines
713 B
Plaintext
17 lines
713 B
Plaintext
# Copyright Security Onion Solutions LLC and/or licensed to Security Onion Solutions LLC under one
|
|
# or more contributor license agreements. Licensed under the Elastic License 2.0 as shown at
|
|
# https://securityonion.net/license; you may not use this file except in compliance with the
|
|
# Elastic License 2.0.
|
|
|
|
{# Fires on salt/key. Only act on successful key acceptance — not reauth. #}
|
|
{% if data.get('act') == 'accept' and data.get('result') == True and data.get('id') %}
|
|
|
|
{{ data['id'] }}_telegraf_pg_sync:
|
|
runner.state.orchestrate:
|
|
- args:
|
|
- mods: orch.telegraf_postgres_sync
|
|
|
|
{% do salt.log.info('telegraf_user_sync reactor: syncing telegraf PG user for minion %s' % data['id']) %}
|
|
|
|
{% endif %}
|