events.action: opened
events.author: et1975
events.text: Serving reactor files via mounted GitFS root exposes the backend logic to minions.
  It seems though that reactors being exposed via the roots is not a _requirement_ for them to function and therefore IMHO is an oversight and a security risk. 
  While there are workarounds and ways to hide sensitive information, it is not enough IMHO. Knowing what backend is doing can be of value by itself to an attacker.
  Would be great to see GitFS configuration for reactors getting the same treatment as the one for pillars - separate, bypassing the root mounts, and being able to include the reactor.conf itself.
events.title: GitFS for Reactors
events.type: issue
events.action: created
events.author: basepi
events.text: You make great points here, and I think this is a great idea. Thanks for the request.
events.type: comment
events.action: created
events.author: mew1033
events.text: This is definitely something I want. Reactors should be store-able in gitfs without exposing them to minions.
events.type: comment
events.action: created
events.author: Da-Juan
events.text: I'm interested in this too!
events.type: comment
events.action: created
events.author: spyd3r
events.text: I'm interested in this feature as well.
events.type: comment
events.action: created
events.author: c4t3l
events.text: +1 internets for this idea!
events.type: comment
events.action: created
events.author: thatch45
events.text: I have added the nitrogen tag here, we would also want to be able to do this with thorium files as well.
events.type: comment
events.action: created
events.author: gtmanfred
events.text: You can put your reactor files in your regular gitfs fileserver, and just reference it using `salt://reactor/whatever.sls`
events.type: comment
events.action: created
events.author: et1975
events.text: I'm confused, in the context of the problem ("hide reactor logic from the minions") what would that accomplish?
events.type: comment
events.action: created
events.author: gtmanfred
events.text: ahh, i missed that part of the feature request, nevermind.
events.type: comment
events.action: created
events.author: et1975
events.text: this issue is closed prematurely.
events.type: comment
data_with_bots.bot: Thank you for updating this issue. It is no longer marked as stale.
data_with_bots.meta: This message directly preceded comment from bot *stale[bot]* by author *et1975*:
data_with_bots.text: this issue is closed prematurely.
data_without_bots.meta: This message directly preceded comment from bot *stale[bot]* by author *et1975*:
data_without_bots.text: this issue is closed prematurely.