You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think potential users of losf would be enticed to try it if there were a way to change the order of actions performed by losf. One example is starting a service that requires specific permissions and system commands run. The desired custom ordering would be something like:
Install package
Sync config files
Set file permissions
Set directory group permissions(x)
Run shell command(x)
Start service
(x) Not supported by losf, but just a thought-experiment.
Ideally in my opinion, losf would not order activity-types like services, permissions, and files. Instead, losf would order individual actions like allowing actions to have a dependency on other actions as puppet and ansible work. If losf were to get this feature, I could imagine the losf philosophy of "keep it simple" would result in something like what I've included below. A numeric "priority" value, with ties broken randomly. The lower the number, sooner losf executes it.
I think potential users of losf would be enticed to try it if there were a way to change the order of actions performed by losf. One example is starting a service that requires specific permissions and system commands run. The desired custom ordering would be something like:
(x) Not supported by losf, but just a thought-experiment.
Ideally in my opinion, losf would not order activity-types like services, permissions, and files. Instead, losf would order individual actions like allowing actions to have a dependency on other actions as puppet and ansible work. If losf were to get this feature, I could imagine the losf philosophy of "keep it simple" would result in something like what I've included below. A numeric "priority" value, with ties broken randomly. The lower the number, sooner losf executes it.
The text was updated successfully, but these errors were encountered: