mach-composer-cli

mach-composer-cli copied to clipboard

At the moment, files that are included (with either `!include` or `${include(..)}`) are not automatically decrypted with SOPS. Just as with variable files, it would be useful if MACH would...

tleguijt

Add variables support

4

MACH should support variables in the configuration to support the following use-cases: - Use CI secrets in your configuration - Use 1 configuration file which can be used over various...

tleguijt

Should we execute individual component deployments with individual IAM AssumeRole (in case of AWS)?

1

To limit permission scope for rolling out individual components, that might be built by different teams, we could consider to execute these with individual set of permissions. Discussed with @mvantellingen

pimvernooij

API gateway v1 supports AWS creating a Cloudfront distribution which sits in front of the API gateway (Edge deployment). Since API Gateway v2 only supports regional endpoints, we would need...

davidweterings

Something we might want to be able to configure in a MACH configuration (or apply certain defaults) **Throttling** - [x] Default route [throttling settings](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/apigatewayv2_stage#default_route_settings) - [ ] Per-route [throttling settings](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/apigatewayv2_stage#route_settings)...

tleguijt

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...

pimvernooij

Add 'architecture guidance' section to the docs

1

We use several architecture design principles in our projects, that we could/should add to the docs. These would be 'generic' best practises when building MACH systems - as even within...

pimvernooij

@mvantellingen showed how easy it is to deploy a Fargate based docker container, for use-cases where AWS Lambda is not sufficient. I suggest we document it and add it as...

pimvernooij

We clone the repo of each component when performing a `mach update`. If we implement the same behaviour during a `mach generate` there are a couple advantages that it brings:...

tleguijt

Couple of challenges: - It is now based on a commit hash. This makes it unclear if a change means a down- or upgrade - From a MACH configuration perspective...

tleguijt