Implement the task struct which should create an id for itself and instanciate executors.
Task is the factory for the executors.

Add function to visualise dag in console :
.........................|[3]
[1]-----[2]-----|
.........................|[4]

Use boltd db to manage all added dag into db :

• Retrieve all dag when init gows
• Add new dag when gows dag add is called
• Remove dag when gows dag remove is called

A proper JSON structured should be defined.
Different types of operator may have different types of configurations.
This problem should be addressed in this issue

Project layout should be modify with a pkg

This module should parse a JSON configuration file and generate a Dag object.
The JSON configuration should have the following format:

{
  "dagName": "hello",
  "schedule": "*/3 * * * * *",
  "operators": [
    {
      "name": "BashOperatorOne",
      "type": "bash",
      "parameters": {
        "cmd": "test.sh",
        "arguments": [
          {
            "arg": "-t",
            "value": "1"
          },
          {
            "arg": "-d",
            "value": "detached"
          }
        ]
      }
    },
    {
      "name": "BashOperatorTwo",
      "type": "bash",
      "parameters": {
        "cmd": "test.sh -t 1 -d detached"
      }
    },
    {
      "name": "PythonOperator1",
      "type": "python",
      "parameters": {
        "src": "test.py",
        "virtualenv": "venv",
        "arguments": [
          {
            "arg": "-t",
            "value": "1"
          }
        ]
      }
    },
    {
      "name": "PythonOperator1",
      "type": "python",
      "parameters": {
        "src": "test.py"
      }
    }
  ]
}

Using this solution, there is no fixed field.
Each operator have their own configuration fields, there is no uniformity among the operators in terms of configuration
fields since we don't use a factory pattern anymore?
This implies to have a strong fields validation process with something similar to this :

if (operator.type == "python") {
   for _, arg := range argsList {
      if (!isArgInConf(operator.type)) {
         return false
     }
   } 
   return true
} 

Another approach would be to have fixed field with a classic unmarshalling.

Given that we didn't use a factory pattern, perhaps the no fixed field approach make more sense.

Implement the task struct which should create an id for itself and instanciate executors.
Task is the factory for the executors.

Implement the CLI to support all the commands.
This is only about the user interaction, there is no need for integration with the core functions of Gows for this issue

• Brainstorm about the CLI possible commands/scenario
• Writing the different scenarios
• Possibly writing the documentation