Deployment with several flavours

[frmadem]

The current situation

The actual deployment system let us to:

1. Define a specif flavour, with a particular Dockerfile and build-args and trigger its construction with an event.
2. Define a tenant-app-env chain to deploy in one or several services names
3. Select a flavour to deploy.

Therefore:

# build-images.yaml
foo:
  triggers:
    push:
      branches: ["master"]
    build_args:
      arg:  "value 1"
      arg2: "value 2"
   dockerfile: Dockerfile.foo

Is going to create an image whenever a push happens master branch.

With this file we can control where the new image is going to be deployed:

# deployment.yml
foo:
  app:
    dev:
      service_names:
        - service1
        - service2
      version: branch_master
      flavour: foo

The image built, following the foo definition on build-images.yaml, is going to be deployed as service1 and service2 in the foo-app-dev tenant-app-env chain.

The problem

We are facing the following situation:

1. The TL wants to build to images (different build-args) for the same trigger and deploy them in different services within the same tenant-app-env.

Therefore,

1. The deployment needs to let us define a particular flavor for every service name.
2. The current system is not enough because it links the same flavour to all the services whitin a particular tenant-app-env chain.

[alambike]

I think you miss one more step in the chain, it should be:
tenant-app-env-slot

Thus, the development team could be able to deploy each flavor in its slot

foo:
  app:
    dev:
      default:
        service_names:
          - service1
        version: branch_master
        flavour: foo
      slot2:
        service_names:
          - service2
        version: branch_master
        flavour: foo2

Also, the development team should define both flavors in the build-image.yaml:

foo:
  triggers:
    push:
      branches: ["master"]
    build_args:
      arg:  "value 1"
      arg2: "value 2"
   dockerfile: Dockerfile.foo
foo2:
  triggers:
    push:
      branches: ["master"]
    build_args:
      arg:  "value 3"
      arg2: "value 4"
   dockerfile: Dockerfile.foo

In this way, with every commit to master 2 deployments should be updated with its correspondent flavor image:

• foo-app-dev-default with the flavor foo
• foo-app-dev-slot2 with the flavor foo2

[alambike]

After conversation we see the need to alter the definition of the deployments.yml to allow specify a list of deployments in the same tenant-app-environment-slot, that we want to update with diferent flavours of the same image, ie:

foo:
  app:
    dev:
      default:
        - name: service1
          service_names:
            - service1
          version: branch_master
          flavour: foo
        - name: service2
          service_names:
            - service2
          version: branch_master
          flavour: foo2

@frmadem in order to generate the v3 of the action, I would go for adding support for the slots coordinate, in addition to the support to be able to modify multiple services in the same slot (<tenant>-<app>-<env >-<slot>) with different flavors.

Another option that I see as less interesting would be to try to get a version v2.1 compatible with both formats of the deployments file, without slots (postponed for a future v3) but with support for a list or a map of service values to modify their image.