Salt: Improve reactor sls files.

Created on 25 Oct 2013  路  10Comments  路  Source: saltstack/salt

Currently reactor sls files are just a big mapping, and can't take advantage on master's module, nor requisite.
Another big improvement would be to log errors when their compilations fail.

Feature

Most helpful comment

some more ideas:

other subsystems have 'root's defined, but not 'reactor'

eg, file_roots, pillar_roots

/etc/salt/master.d/reactor.conf
reactor_roots

instead of keeping the configs local on the master, make a top file to define the reactions mapping and make them available to the minions as well, via URI style like the rest of the subsystems

/srv/reactor/top.sls <

my-reactions:

<#


??

All 10 comments

This would be very useful! Thanks!

some more ideas:

other subsystems have 'root's defined, but not 'reactor'

eg, file_roots, pillar_roots

/etc/salt/master.d/reactor.conf
reactor_roots

instead of keeping the configs local on the master, make a top file to define the reactions mapping and make them available to the minions as well, via URI style like the rest of the subsystems

/srv/reactor/top.sls <

my-reactions:

<#


??

I'd be making heavy use of requisites if they were available and am currently trying to find some ugly hacks to remake this. Other roots like gitfs is also something I'd make use of. Sorry, but this is sort of a 'me too' comment.

I would also love to see what @CDSRV mentioned regarding top.sls for reactors.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

https://docs.saltstack.com/en/latest/topics/reactor/#where-to-put-reactor-sls-files

it seems reasonable and consistent to supply a parameter for search paths rather than repeat the path prefixes everywhere.

Thank you for updating this issue. It is no longer marked as stale.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

Feature request is still valid

Thank you for updating this issue. It is no longer marked as stale.

Was this page helpful?
0 / 5 - 0 ratings