Create 'runtime terraform modules' for different runtimes we support

[pimvernooij]

MACH composer currently contains some assumptions about the runtime components are deployed in. The advantage of this is that we can maintain these assumptions on a single place, so that when something changes, we only have to change it once.

The disadvantage of this is that users of mach composer are 'bound' by what we determine within mach composer.

In order to decouple this from mach composer, the proposal is to create terraform modules for the runtimes that could be used.

Perhaps create a separate repo for that? i.e. mach-composer-terraform-modules? Not sure what is 'best practise'.

We could offer modules for:

• mach-azure-functionapp
• mach-aws-lambda (which itself should be using the https://github.com/terraform-aws-modules/terraform-aws-lambda module? or should we recommend to just use that module always? There seems to be 'generic' MACH configuration that we might want to have in a module) -mach-aws-fargate

These modules could then be included in components, or you can choose for rolling your own (or forking a module that we provide to cater for your own needs).