Maestro Blog

Maestro team has been constantly monitoring and carefully analyzing offerings and tendencies of the market. Currently, we have noticed, that Terraform Enterprise became the top and promising solution, being in great demand among virtual infrastructure users. During Maestro earlier and present presales activities, we quite often get questions about how Maestro works with Terraform Enterprise, or whether we have a substitute or replacement of it in our application. What benefits does Maestro have compared to Terraform Enterprise? VCS Connection TFE: VCS connection in Terraform Enterprise allows users to write, version, review, collaborate on code. Automate and trigger runs through the connection between Terraform and major VCS providers. M: Maestro is integrated with GitHub and allows users to work with it as a source for taking Terraform templates . Maestro works not only with a single file but with large amounts of files located in different folders. Folde

In the first part of this article, we talked about Workspaces, Private Module Registry, and VCS Connections in Terraform Enterprise and Maestro Terraform.  In this part we will proceed, discussing such important features as API Endpoints, Policy as a Code,  Variables, and  Runs and State.  Variables TFE: Granular variables allow easy reuse of code to scale resources, regions, etc. All variables are securely stored and retrieved as needed during the provisioning process. M3: Maestro fully supports working with variables . Needless to say, Terraform templates are impractical if we create them for one-time use. For example, if the template is stored in a GitHub repository, it can be reused by other users. To reuse an existing template, you should set the specific configuration for your environment. Generally, when creating a template it is a best practice to move such a configuration into variables. For example, with variables, we can indicate, the name of our instance, reso

In the third and the last part of this article, we will talk about Policy Enforcement, Cost Estimation, Notifications, SAML Integration and other functionality without which we cannot imagine handling the virtual infrastructure management routine. Notifications TFE: Triggers external notifications . Provides support of Slack calls and webhooks. M3: Maestro supports the notifications functionality upon different events occurring in the system, such as: Terraform template execution, resources deployment from the Terraform template, running/stopping an instance, etc. We have implemented a set of notifications that is sufficient for working with the Maestro system. Currently, we support emails and push-notifications. The support of other systems can be easily implemented. Terraform Enterprise Provider TFE: Automates workspace provisioning. Presents a Terraform provider that allows flexible workflow and configuration. M3: Maestro  from its side supports the same workflow as