kilgaloon / leprechaun Goto Github PK

Remove startIn from recipes

Make use of go plugins and create mechanism to extend usage of notifications and posibility to add new notification systems through plugins

Prioritize tasks with following specifications.

If all workers are already populated to maximum, and some high priority task is standing in queue to be executed, take lowest priority task and stop it, move it to queue and wait available worker slot to continue on that task.

Started task can't be paused (needs more investigation), this can be killed and restarted again.

Enable webhooks to trigger recipes, also these recipes can't be scheduled

• Config validator
• Recipe validator

Recipe validator should run before in BuildQueue and AddInQueue to check is recipe is valid

Rename all functions with Create{Placeholder} -> New

Use yml format inside *.lock file.

Informations in file:

• Started
• Current step
• Errors
• ErrorMessage (empty if Errors != true)
• Finished (If finished properly)

If we implement this, we will know did recipe finished properly, next time we can know which recipes to push to queue and which not.

This can take a Locking recipe functionality into considiration for change.

Issues that can be affected: #30 #31

Generate report for every finished recipes with detailed info

• Create method that will write PID to pid file and set it in client struct.
• Rewrite GetPID method to return PID from struct, not to read from pid file every time.

socket.Registrator now has method Command where we specify commands for our app, extend command defining to provide description on how to use specific command.

This will be used to display each command and description for it when command help is passed

Wrapper for this already exists.

Take a look at client/commands.go

With latest updates server is supported with basic commands that are coming with agent

Every stdout of application needs to end up in info.log

Handle signal for terminating program and do cleanup

Display status of client:

• Started at
• Number of workers currently working
• Recipe currently working
• Memory usage
• CPU informations for current process

In this case we can use config for other services.

Define how many workers can be spawned.

This can cause that some recipes can't be finished on time, if there is a lot of recipes happening in same time.

App needs to have opened socket to be available to receive commands from outside

• Every X days
• Specific day of week
• Every day at X hours
• Specific day at X hours
• Every week at specific day
• Every month at specific day

Client

• Client/Start
• Client/Stop
• Client/GetPID
• Context
• Lock
• Main
• Queue
• Config
• Log
• Recipe/Reader
• Recipe/Schedule
• Config/Validate
• Workers

This should be somewhere in recipe file, expand step definitions, but we need to have somewhere to defined which task is sync/async.

sync is by default

Only one instance of leprechaun can run on system.

Generating .pid file gives us ability to create stop command when process is running in background

Example:

echo "some string" > ./file.txt

"some string" will be split and act as 2 different arguments "some and string" and command wont work as expected

Recipe definition cron and support same pattern for scheduling recipes

.lock file appears when there is no recipes to be executed

1. Ask him is here sure?
2. If there is some recipe working, notify him that recipe is working and ask again is he sure

Make usage of plugins and ability to extend leprechaun functionality