Azure deployments¶
Resource groups¶
MACH will create a resource group per site.
Only when a resource_group
is explicitly set, it won't be managed by MACH.
HTTP routing¶
Only when a MACH stack contains components that have an endpoint
defined, MACH will setup a Frontdoor instance to be able to route traffic to that component.
Default endpoint¶
If you have defined your component with a default
endpoint, MACH will create a Frontdoor instance for you which includes the default Azure domain.
components:
- name: payment
source: git::ssh://git@github.com/your-project/components/payment-component.git//terraform
endpoints:
public: default
version: ....
This default
endpoint doesn't need to be defined in your endpoints definition.
Custom endpoint¶
Whenever a custom endpoint from your endpoints definition is used, MACH will require that you have configured frontdoor
for additional DNS information that it needs to setup your Frontdoor instance.
In addition to that it will also setup the necessary DNS record.
Routes to the component¶
For each component with an endpoint
the MACH composer will add a route to the Frontdoor instance using the name of the component.
So when having the following components defined:
components:
- name: payment
source: git::ssh://git@github.com/your-project/components/payment-component.git//terraform
endpoints:
public: main
version: ....
- name: api-extensions
source: git::ssh://git@github.com/your-project/components/api-extensions-component.git//terraform
version: ....
- name: graphql
source: git::ssh://git@github.com/your-project/components/graphql-component.git//terraform
endpoints:
public: main
version: ....
The routing in Frontdoor that will be created:
App service plan¶
MACH will create an App service plan that can be used for any MACH component that implements an Azure function.
Action groups¶
When an Alert group is configured, an Action group will be created.
Components can use that action group to attach alert rules to.