jaeg / hats-worker Goto Github PK

In an attempt to make this work better with kube we should gracefully shutdown the node and free up in scripts that might be running to better assist in minimizing their downtime.

Right now threads run continuously with no control over when they run, how often they run, and how fast they loop again.

New Thread fields:

• NumberOfCycles : How many times to loop when a thread is ran. -1 to not stop looping.
• Frequency: Follow cron job formatting.
• CycleDelay: How long to wait between loops.
• DeadSeconds: Amount of time between heartbeats to consider thread dead.

This will be helpful when we need secrets or other information to connect to things such as DBs and don't want them hard coded.

Not sure if it should keep supporting code being hosted in redis. I think requiring hatbox to run is reasonable given the nature of hats.

Handle private keys, be able to ssh into other machines and execute commands.

We need JS api hooks to allow users to store and retrieve files from a hatbox that is connected to the system.

Things to include:

• RDS
• MQ as a possible way to trigger scripts to run and add the ability for scripts to trigger events.
• SES
• S3

To allow scripts to have dependencies implement a version of "require" that either looks up the code from disk or redis and runs it in the otto vm to get it into memory and usable by other parts of the script.

We need new fields for Threads. Error date, Error Text. On a script failure put both of these in redis.