{"id":108,"date":"2024-05-21T08:30:09","date_gmt":"2024-05-21T15:30:09","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/develop-from-the-cloud\/?p=108"},"modified":"2024-05-21T08:45:35","modified_gmt":"2024-05-21T15:45:35","slug":"customized-project-specific-templates-in-azure-deployment-environments","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/develop-from-the-cloud\/customized-project-specific-templates-in-azure-deployment-environments\/","title":{"rendered":"Boost dev team agility with customized, project-specific templates in Azure Deployment Environments"},"content":{"rendered":"

Have you heard the latest news about Azure Deployment Environments? Last month, we released an extensibility model that\u2019s set to transform how platform engineers tailor deployments to their organization\u2019s unique needs. This new model empowers you to customize deployments using any infrastructure-as-Code (IaC) framework you prefer\u2014whether that’s Bicep, Terraform, or any other popular IaC or scripting tool. And it\u2019s incredibly user-friendly, requiring just a few simple steps to unlock its full potential.<\/span><\/p>\n

The goal of the extensibility model was to give organizations more powerful, flexible ways to define and tailor environment templates for app dev projects, and you can learn more about it in the blog we released last month<\/a>.<\/span><\/p>\n

Today, we\u2019re excited to announce new capabilities that are built on our extensibility model. These new features give dev teams the flexibility to leverage templates that are more customized to their projects and make it easier to get started with service.<\/span><\/p>\n

Read on to learn how these new capabilities in Azure Deployment Environments unlock several benefits for development and platform teams alike.<\/span><\/p>\n

Expanding the extensibility model to Pulumi<\/strong><\/span><\/h3>\n

Today, we\u2019re very excited to announce the expansion of our extensibility model to Pulumi. In addition to first class support for Azure Resource Manager (ARM) and Bicep<\/a>, and guidance on performing Terraform deployments<\/a>, customers can now easily perform Pulumi deployments using ADE\u2019s extensibility model.<\/span><\/p>\n

Pulumi is easy to adopt and use as it allows you to write infrastructure-as-code in the language you are most comfortable with\u2014like TypeScript, JavaScript, Python, Go, or C#\u2014or convert existing templates from ARM, Terraform, and other formats. Pulumi offers a simplified, accelerated way to deploy infrastructure in Azure through Deployment Environments.<\/span>\"ADE<\/a><\/span><\/p>\n

We\u2019ve partnered with Pulumi to make it easier for customers to leverage the extensibility model in Deployment Environments. You can now either directly use the standard Pulumi image<\/a> or build your own container image by leveraging workflows published by Pulumi<\/a>. This feature is in preview, and we\u2019re eager to see what customers will accomplish with it.\u00a0 Read Pulumi\u2019s blog<\/a> to learn more and give Pulumi a try today with Deployment Environments<\/a>. You can also get a direct download on how to perform Pulumi deployments in Deployment Environments by registering for the workshop hosted by Pulumi<\/a>.<\/span><\/p>\n

Adding private registry support<\/strong><\/span><\/h3>\n

In addition, we\u2019re building out our extensibility model by announcing support for private registries today. While the extensibility model allows you to configure images in any IaC framework you want, you can now bring these container images into Deployment Environments through a private registry for more controlled access. Sign up for private preview today<\/a> to try out private registries in Deployment Environments. \u00a0<\/span><\/p>\n

Increasing team agility with project-level catalogs<\/strong><\/span><\/h3>\n

With Azure Deployment Environments, our goal has always been to empower dev teams with a seamless, intuitive way to provision app infrastructure within enterprise guardrails. Today, we are excited to introduce project-level catalogs that further enhance dev team access to the app infra they need. You can attach repos as catalogs directly to projects and deliver templates that are tailored to the unique needs of different dev teams.<\/span><\/p>\n

\"Image<\/a><\/p>\n

Better yet, you can give dev leads the ability to directly customize their team\u2019s templates. In turn, this can significantly increase dev team agility by ensuring they have the precise app infra they need and enabling dev teams to be more autonomous\u2014all without compromising on governance. This feature is in preview, and you can learn more by reading our docs about how to configure project-level catalogs<\/a>.<\/span><\/p>\n

Delivering catalog enhancements<\/strong><\/span><\/h3>\n

On top of all that, we’re also introducing capabilities to further improve the experience of setting up and managing catalogs in Deployment Environments, such as:<\/span><\/p>\n