An Automation stack is a resource (or collection of resources) designed to modify your cloud environment in response to pre-defined triggers. These triggers may be alerts detected in logs, timed maintenance activities, or new resource creation events. The role of the Automation stack is to deliver:
- Automated service recovery and issue escalation tasks.
- Resource behaviours that simplify common management tasks.
- Configuration data for setting up new resources.
An operational Automation stack is an essential part of the Core Building Block. Predefined tag-based behaviours are dependent on the Automation stack, which also serves as an extension point for custom behaviours and tasks.
Cloudmarque workload components use a service locator pattern to identify the services they provide and specify dependencies. This component provides and relies on the following services:
- Keys - A secret store is required to authorise the automation accounts to access the wider cloud environment.
- Logging - A logging service is required as a target for alerts when automations succeed or fail.
Edit this page on GitHub
The content on this page is published under Open Source licenses via GitHub. To submit issues or provide feedback please visit the repository.Visit