pulumi · cnunciato · Jun 27, 2026
diff --git a/content/blog/cloud-engineering-fuels-startup-innovation/index.md b/content/blog/cloud-engineering-fuels-startup-innovation/index.md
@@ -38,6 +38,8 @@ tags:
 ---
 The story of how the cloud fuels startup innovation seems never ending. In the beginning, AWS birthed cloud computing with its first service, SQS, in 2004 and quickly released several additional services (like S3, EC2, and SimpleDB). From this innovation, startups flourished because they were able to build, experiment, and grow faster than before at much lower cost. Airbnb, Netflix, Zynga, and many more were born, and the rest is history.
 
+{{% hcl-note %}}
+
 Today, a new generation of startups is flourishing because of the cloud, but this time with modern cloud architectures that are distributed, API-driven, and more resilient and scalable than ever. Today’s startups have to get to market even faster and rapidly innovate in order to delight customers and carve out market share. Most startups understand the benefits of adopting the modern cloud to help them achieve this goal. However, their ability to reap these benefits for competitive advantage depends on how well they can harness the modern cloud.
 
 Within the [cloud engineering](/cloud-engineering/) community, we see several common patterns for harnessing the modern cloud. Some startups have teams of full-stack developers who need to deploy cloud infrastructure and applications safely and at high velocity. Others might have a few infrastructure or platform engineers who need to enable other developers to use cloud infrastructure easily on a self-serve basis. Many of these teams started off using domain-specific languages (DSLs) to manage infrastructure as code and quickly found that these languages were the limiting factor in achieving faster velocity. DSLs are cumbersome to use and don’t support the logic and expressiveness needed to build and manage modern architectures that are more complex in nature. DSLs are also a barrier to entry to most developers.

diff --git a/content/blog/cloud-engineering-on-the-rise/index.md b/content/blog/cloud-engineering-on-the-rise/index.md
@@ -14,6 +14,8 @@ One of the most fulfilling aspects of working at Pulumi is learning how customer
 
 <!--more-->
 
+{{% hcl-note %}}
+
 Pulumi is born from the experiences and needs of teams practicing cloud engineering every day. When we [announced](/blog/pulumi-3-0/) the Pulumi Cloud Engineering Platform in April, CEO & Founder Joe Duffy [talked about](https://www.youtube.com/watch?v=Zko70KVGcgo) bringing cloud engineering to everyone. Over the past year we have seen significant growth in cloud engineering and usage of Pulumi across companies of all industries and sizes, and spanning a diverse spectrum of teams and engineering disciplines. We’re also seeing growing numbers of job postings with “cloud engineer” in the title or which have Pulumi as a requirement or desired skill set.
 
 Recently, we published several case studies about how teams are applying cloud engineering best practices. Cloud engineers apply standard software engineering practices and tools uniformly across infrastructure management, application development, and security to tame the complexity of delivering and managing modern cloud applications. We’ve published on our [website](/cloud-engineering/) and in this [blog](/blog/infrastructure-testing-concepts/) some of the key cloud engineering best practices that we see broadly across the community, and encourage you to read further to see three stories of cloud engineering in action.

diff --git a/content/blog/config-chaos-to-programming-languages/index.md b/content/blog/config-chaos-to-programming-languages/index.md
@@ -22,6 +22,8 @@ social:
 
 *This post is based on our video interview with Daniel Ward, a Software Developer/Consultant at Lean TECHniques and Microsoft MVP. Daniel shares his strategies for moving teams from configuration chaos to programming languages for infrastructure, including the 10% rule for change, viral adoption, and why Pulumi beats YAML for complex systems. Watch the video below or read on. - Adam Gordon Bell*
 
+{{% hcl-note %}}
+
 {{< youtube "3VKbaNtbdSs?rel=0" >}}
 
 Imagine your infrastructure codebase has evolved from a few files to thousands of lines across dozens of configuration files. Your team spends hours deciphering CloudFormation templates, your AWS CDK deployments take 30+ minutes, and introducing any change becomes a multi-day effort. This is the reality many organizations face when their infrastructure-as-code approach outgrows their tooling.

diff --git a/content/blog/getting-started-aks-pulumi-csharp/index.md b/content/blog/getting-started-aks-pulumi-csharp/index.md
@@ -35,6 +35,8 @@ social:
 
 <!--more-->
 
+{{% hcl-note %}}
+
 Live demos keep you honest. On June 10th my AKS workshop went a little sideways. Partway through, Docker Hub rate-limited my image pull and we had to adapt the content on the fly. The original plan was to stand up an AKS cluster with Cilium, an Azure Container Registry with the cluster's pull permission wired in code, and a random-cat web app, then split the infrastructure from the workload into separate Pulumi stacks. Live, we didn't make it through all of that, but we had some fun tangents and it turned out to be a great session. So here are my six recommendations for working with Kubernetes on Azure from this recent workshop.
 
 ## 1. Pick the language your team already uses

diff --git a/content/blog/gitops-best-practices-i-wish-i-had-known-before/index.md b/content/blog/gitops-best-practices-i-wish-i-had-known-before/index.md
@@ -36,6 +36,8 @@ Getting started with GitOps can feel like trying to herd cats through a YAML fac
 
 <!--more-->
 
+{{% hcl-note %}}
+
 If you're not familiar with the formal definition, the [OpenGitOps](https://opengitops.dev/) project distills it into four principles:
 
 * Declarative desired state

diff --git a/content/blog/hcl-vs-pulumi/index.md b/content/blog/hcl-vs-pulumi/index.md
@@ -29,6 +29,8 @@ tags:
 The Java Language Architect at Oracle, Brian Goetz, author of Java Concurrency in Practice, has commented how declarative
 languages can be a double-edged sword:
 
+{{% hcl-note %}}
+
 ![brian-goetz-tweet](brian-goetz-tweet.png)
 
 HashiCorp’s infrastructure as code solution, Terraform, uses a domain-specific language (DSL) to declare cloud

diff --git a/content/blog/hidden-costs-of-infrastructure-management/index.md b/content/blog/hidden-costs-of-infrastructure-management/index.md
@@ -15,6 +15,8 @@ Note: This post discusses Pulumi Copilot, which Pulumi Neo has replaced. [Learn
 
 [Infrastructure as Code (IaC)](/what-is/what-is-infrastructure-as-code/) has revolutionized how cloud resources are managed, allowing for more efficient, scalable, and repeatable deployments. We designed [Pulumi IaC](/product/infrastructure-as-code/) to let you program cloud infrastructure using familiar programming languages like TypeScript, JavaScript, Python, Go, .NET, Java, and YAML. This approach not only simplifies the process but also integrates seamlessly with existing development tools and ecosystems (e.g., IDEs, standard unit test frameworks, integration test). You can define infrastructure with code, often in just one line, for serverless, Kubernetes, AI/ML, databases, and more. You can also preview changes before deploying unlike many other IaC solutions. Pulumi IaC is fully open source with a [public roadmap](https://github.com/orgs/pulumi/projects/44/). We value working with the community to shape the product through feedback and contributions.
 
+{{% hcl-note %}}
+
 ## What is Pulumi Cloud?
 
 Infrastructure as Code tools like Pulumi require systems for coordinating deployments, which include concurrency control, state management, and security. For the purposes of this post, let's refer to these systems as IaC backends. There are several options for managing these backends: you can either handle them yourself, which we'll call DIY, or you can leverage [Pulumi Cloud](/product/pulumi-cloud/), available as a SaaS or self-hosted solution. With Pulumi Cloud, you gain access to a comprehensive infrastructure management platform designed to handle everything running in the cloud. This platform automates your IaC deployments, centralizes [secrets management](/what-is/what-is-secrets-management/) and orchestration to manage secrets sprawl effectively, and employs AI to oversee infrastructure assets and ensure compliance. On the other hand, with a DIY approach, you have the flexibility to build everything Pulumi Cloud offers or opt for a more minimalistic setup tailored to your organization's specific needs. Both options are well-supported by Pulumi, but there are distinct advantages to choosing Pulumi Cloud over the DIY method, which we'll explore further.

diff --git a/content/blog/infrastructure-as-code-tools/index.md b/content/blog/infrastructure-as-code-tools/index.md
@@ -21,6 +21,8 @@ Infrastructure as Code (IaC) has evolved beyond simple automation into a fundame
 
 <!--more-->
 
+{{% hcl-note %}}
+
 As infrastructure complexity grows, teams increasingly seek approaches that provide the same developer productivity tools they use for application development. While template-based and domain-specific language approaches serve many use cases effectively, teams with complex requirements or programming backgrounds often find that general-purpose programming languages offer advantages in testing, abstraction, and collaboration.
 
 This comprehensive guide examines the most effective infrastructure as code tools available today, providing detailed analysis of core IaC platforms, complementary tools, and related technologies through the lens of software engineering best practices. Whether you're starting fresh with IaC or evaluating alternatives to overcome limitations in your current toolchain, we'll help you navigate this complex landscape and choose solutions that truly bring software engineering to infrastructure.

diff --git a/content/blog/migrating-my-infrastructure-from-terraform-to-pulumi/index.md b/content/blog/migrating-my-infrastructure-from-terraform-to-pulumi/index.md
@@ -16,6 +16,8 @@ Pulumi community member [Erik Näslund](https://blog.ekik.org/) shares his thoug
 
 <!--more-->
 
+{{% hcl-note %}}
+
 I've been using [Terraform](https://www.terraform.io/) for a couple of years and overall I've been quite happy with it. However there's a few things that started to bother me more and more recently.
 
 Terraform uses a language called Hashicorp HCL to define the infrastructure. It's a relatively simple declarative language, but it's something I had to learn along the way. Just like any language it has it's little quirks, and I often found myself spending more time than I wanted to figure out how to do certain things. As I'm doing all the infrastructure myself I really wanted to be able to use a language I'm familiar with, to make things simple.

diff --git a/content/blog/next-level-iac-briding-the-declarative-gap/index.md b/content/blog/next-level-iac-briding-the-declarative-gap/index.md
@@ -19,6 +19,8 @@ Pulumi stands out in the world of infrastructure-as-code (IaC) for its flexibili
 
 <!--more-->
 
+{{% hcl-note %}}
+
 In Pulumi, you describe your infrastructure in code – real code, not a [DSL][dsl-wiki] or [YAML][yaml-wiki] – using your preferred general purpose programming language. You don't have to become a specialist in a niche proprietary declarative language, like Terraform's HCL. Rather, you can reuse your existing programming skills, writing in standard imperative, object-oriented, and even [functional language][fsharp-example] styles, while still gaining all of the benefits of the declarative style that other tools emphasize.
 
 Pulumi provides a unique mix of a [declarative model][pulumi-declarative-imperative-docs] embedded and implemented inside of a standard programming language, allowing all the flexibility of custom imperative code, while still enabling Pulumi's [deployment engine][pulumi-engine-docs] to infer opportunities for parallel asynchronous execution and to converge a partially-realized system.

diff --git a/content/blog/next-level-iac-package-ecosystems/index.md b/content/blog/next-level-iac-package-ecosystems/index.md
@@ -18,6 +18,8 @@ tags:
 
 Every experienced tech professional I know has a programming language they love. But is it the syntax and symbols that make it so loveable? Not really. It's the community and package ecosystem surrounding the language that makes a real impact on your heart... and on your productivity!<!--more--> If we look at some of the biggest success stories in tech --- Python, Node.js, Ruby, Perl, and Go --- the common thread between all of them is an extensive ecosystem of packages, libraries, modules (or whatever you decide to call them…  ahem, Gems?!). A great language will allow you to build anything you can imagine, but a great ecosystem will have already written it for you, and made it available in a convenient to install-and-use package.
 
+{{% hcl-note %}}
+
 ![Pulumi Language Ecosystem](pulumi-language-ecosystem.png)
 
 One of the amazing things about Pulumi is that it is built around general-purpose programming languages, and that means your Pulumi programs have access to the entire ecosystem of packages that come with each language. This is a stark difference between Pulumi and other infrastructure automation tools that use proprietary domain-specific languages with not much in the way of community around them. Some tools might allow you to write custom code, but they certainly don’t make it convenient, and still… you have to write it yourself, which just adds so much overhead to a project where your core concern isn’t writing that custom function, but rather shipping your own product on the infrastructure you are trying to automate.

diff --git a/content/blog/pulumi-for-aws-automate-secure-manage/index.md b/content/blog/pulumi-for-aws-automate-secure-manage/index.md
@@ -22,6 +22,8 @@ Stop by the Pulumi re:Invent booth #370 this week to chat with experts on the Pu
 
 <!--more-->
 
+{{% hcl-note %}}
+
 ## Why Pulumi for AWS?
 
 Pulumi empowers your organization to automate AWS cloud infrastructure through code, tame secrets sprawl through centralized secrets management, and manage cloud assets and compliance with the help of AI. Pulumi encourages infrastructure, platform, development, DevOps, and security teams to collaborate and accelerates time to market with greater control and minimized risk.

diff --git a/content/blog/the-superintelligence-flywheel/index.md b/content/blog/the-superintelligence-flywheel/index.md
@@ -26,6 +26,8 @@ The infrastructure required to build superintelligence demands superintelligence
 
 <!--more-->
 
+{{% hcl-note %}}
+
 The systems being built today for superintelligence are already straining human platform teams to their limits and yet we're still only just getting started. To succeed, we will have no choice but to use AI itself to help us manage the infrastructure scaling ahead on the path to superintelligence.
 
 Superintelligence demands more infrastructure, which demands superintelligent approaches to managing and scaling that infrastructure, which leads to faster progress towards superintelligence.

diff --git a/content/blog/why-switch-to-pulumi/index.md b/content/blog/why-switch-to-pulumi/index.md
@@ -33,6 +33,8 @@ are bogged down by:
 - Rolling out updates across regions takes weeks
 - The combinations of modern cloud architectures seems infinite
 
+{{% hcl-note %}}
+
 You know there has to be a better way. A way to truly
 harness the power of the cloud and turn it into your competitive
 advantage.

diff --git a/...ulumi-whats-the-smart-choice-for-deployment-automation-with-kubernetes/index.md b/...ulumi-whats-the-smart-choice-for-deployment-automation-with-kubernetes/index.md
@@ -55,6 +55,8 @@ YAML and [Kubernetes](https://kubernetes.io/) go together like peanut butter and
 It's often the first tool developers encounter when diving into Kubernetes, and for good reason - its human-readable format makes it the preferred choice in most tutorials, documentation, and even production deployments.
 <!--more-->
 
+{{% hcl-note %}}
+
 <div style="display: flex; align-items: center; justify-content: center; height: 600px;">
     <img src="yaml.png" alt="Description of image" style="width: 60%; height: 100%">
 </div>

diff --git a/content/case-studies/bmw.md b/content/case-studies/bmw.md
@@ -23,7 +23,7 @@ aliases:
 
 As organizations scale their cloud infrastructure, they face a critical choice: continue managing infrastructure and applications as separate concerns with different tools and workflows, or unify them under a single, programmable approach. Traditional infrastructure-as-code tools require learning proprietary languages and often force teams to maintain parallel toolchains for application deployment and infrastructure provisioning.
 
-Platform engineering teams need solutions that can scale to thousands of resources across multiple environments while maintaining security, compliance, and developer productivity. They need the full power of real programming languages, not limited domain-specific languages. And they need infrastructure that integrates naturally with their existing CI/CD pipelines rather than requiring separate automation workflows.
+Platform engineering teams need solutions that can scale to thousands of resources across multiple environments while maintaining security, compliance, and developer productivity. They need the full power of general-purpose programming languages, with the libraries, tooling, and abstractions those languages provide. And they need infrastructure that integrates naturally with their existing CI/CD pipelines rather than requiring separate automation workflows.
 
 ## About CodeCraft
 

diff --git a/content/cloud-engineering/_index.md b/content/cloud-engineering/_index.md
@@ -27,7 +27,7 @@ build:
         - title: General-Purpose Programming Languages
           description: |
             Define infrastructure with general-purpose programming languages like TypeScript/JavaScript, Python, Go, .NET, and Java and use standard constructs like loops
-            and conditionals. This gives you more flexibility and reduces complexity compared to domain-specific languages. You could also use markup languages like YAML as a simple way for consuming complex infrastructure modeled in general-purpose languages. 
+            and conditionals. This gives you the flexibility of loops, functions, and conditionals when you want them. You can also use a markup language like YAML, or a domain-specific language like HCL, depending on what fits your team. 
 
         - title: Broad Development Ecosystem
           description: |

diff --git a/content/docs/iac/comparisons/opentofu.md b/content/docs/iac/comparisons/opentofu.md
@@ -55,7 +55,7 @@ OpenTofu is an open-source, declarative infrastructure as code tool forked from
 
 ### Language support and the authoring experience
 
-OpenTofu configurations are written in [HCL](https://opentofu.org/docs/language/), a declarative DSL with a fixed set of [built-in functions](https://opentofu.org/docs/language/functions/) and meta-arguments (`for_each`, `count`, `dynamic`) for shaping resources. The DSL keeps configurations declarative but constrains abstraction: there are no classes, no first-class testing frameworks, and no general-purpose package ecosystem. Pulumi programs are written in general-purpose languages, so authors get loops, conditionals, classes, package management, IDE features (autocomplete, type checking, refactoring, go-to-definition), and the testing frameworks that already exist in those ecosystems. Pulumi also supports [YAML](/docs/iac/languages-sdks/yaml/) for users who prefer a markup format.
+OpenTofu configurations are written in [HCL](https://opentofu.org/docs/language/), a declarative DSL with a fixed set of [built-in functions](https://opentofu.org/docs/language/functions/) and meta-arguments (`for_each`, `count`, `dynamic`) for shaping resources. HCL is declarative and configuration-focused. General-purpose languages offer a different model, with classes, richer runtime logic, package management, IDE features (autocomplete, type checking, refactoring, go-to-definition), and the testing frameworks that already exist in those ecosystems, so Pulumi lets you choose the approach that fits the project. Pulumi supports HCL natively as well, alongside [YAML](/docs/iac/languages-sdks/yaml/) for users who prefer a markup format.
 
 ### Cloud and service coverage
 
@@ -77,7 +77,7 @@ Pulumi treats secrets as a first-class primitive. Values marked as secrets are e
 
 ### Modularity and reuse
 
-OpenTofu modules are units of HCL referenced from a local path, a Git URL, or a registry. They compose well within HCL but cannot share runtime helpers or types with non-module code. Pulumi's [Component Resources](/docs/iac/concepts/components/) are runtime objects with explicit parent/child relationships, so a component and the resources inside it form a coherent unit in plan output, deletion, and state. Components can be authored in one language and consumed from any other supported language by publishing them as a [Pulumi Package](/docs/iac/concepts/packages/). Pulumi can also [consume OpenTofu modules directly](/docs/iac/guides/building-extending/using-existing-tools/use-terraform-module/), automatically installing and invoking OpenTofu to execute them — useful for teams that have invested heavily in module libraries and want to keep using them while moving to Pulumi.
+OpenTofu modules are units of HCL referenced from a local path, a Git URL, or a registry. Modules compose within HCL. Pulumi's [Component Resources](/docs/iac/concepts/components/) are runtime objects that can share helpers and types with the rest of your program, with explicit parent/child relationships, so a component and the resources inside it form a coherent unit in plan output, deletion, and state. Components can be authored in one language and consumed from any other supported language by publishing them as a [Pulumi Package](/docs/iac/concepts/packages/). Pulumi can also [consume OpenTofu modules directly](/docs/iac/guides/building-extending/using-existing-tools/use-terraform-module/), automatically installing and invoking OpenTofu to execute them — useful for teams that have invested heavily in module libraries and want to keep using them while moving to Pulumi.
 
 ### Automation API