In order to rollback, we need to specify the revision.

• Add field revision in DB
• After each helm upgrade/rollback we increment the revision by 1 in the finalizeUpgrade
• On rollback, we get the last release for the deployment in the namespace, we read the revision number and we do a helm rollback $releaseName $revision—

Input

Deployment name

Output

Deployment

Ref: https://github.com/vgheri/gennaker/wiki/Slackbot-commands

Slack command

list

Input

Nothing

Output

List of deployment names formatted as a bulleted list

"attachments": [
        {
            "title": "My title",
            "pretext": "Pretext _supports_ mrkdwn",
            "text": "• Testing \n • Testing 2",
            "mrkdwn_in": [
                "text",
                "pretext"
            ]

Input

• Query string: limit, offset

Output

• List of deployment without status, just minimal set of info

Something like

{
  "reports": [
    {
       "namespace": "int",
       "status": "deployed",
       "message": "blablalblabla"
     }
  ]
}

Input:

• Deployment Name
• Docker image tag
• Release values e.g. [{"key": "value"}, {"key": "value"}...]

Behaviour:

1. The system checks the deployment exists. If not, HTTP 400 Invalid Deployment
2. The system reads the pipeline related to the deployment to retrieve root namespace(s).
3. The system issues a helm InstallOrUpgrade command on each namespace
4. The system starts the helm command and returns HTTP 200 to the client as soon as helm command returns.

Output:
-HTTP 200 Release started.

The gennaker.yml file contains the deployment pipeline as code.
Once parsed, it should be a valid deployment pipeline used by the engine to know what to do upon a deploy command is received.

I like the ideas behind this project and would be willing to help develop it if it's still active.

Input:

• Deployment id
• From namespace
• Overwrite values [{key, value}, {key: value}...]

Behaviour:

• The system retrieves the chart, retrieves the docker image and tag part of the latest release in the "from namespace" and applies the overwrite values to helm upgrade --install

Output:

• 201 Created and return the new release

Input:

• chart name
• chart repository url

Behaviour:
The system should retrieve the chart, access the gennaker.yml file, parse it, build the deployment pipeline and populate the db.

Output:

• 200 OK and the deployment ID
  OR
• 4xx/5xx error if any

If revision is specified, we promote a specific revision, otherwise the latest one.