# terraform provider A Terraform provider is a plugin that lets Terraform interact with cloud providers, SaaS providers, and other APIs, exposing resources and data sources for infrastructure management. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Compatibility Testing Pulumi HCL DevFeed: [Compatibility Testing Pulumi HCL]() Original publisher: [Read original article]() Author: Ian Wahbe Published: 2026-08-14T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [Testing](), [opentofu](), [Terraform](), [terraform provider](), [Code]() Tags: [code](), [engineering](), [hcl](), [opentofu](), [terraform](), [terraform-provider](), [testing]() ### AI overview The article explains a compatibility-testing approach for Pulumi HCL. It defines correctness as Pulumi HCL and OpenTofu generating the same Terraform provider steps from the same HCL program, then describes tests that compare provider configuration and RPC behavior. ### Source excerpt Pulumi HCL has at its core a simple promise: A program that works for tofu apply will also work for pulumi up. This must be true to allow Terraform modules to be shared between tofu config and Pulumi programs. This property makes testing Pulumi HCL simple. Let me explain. At the end of the day, Pulumi is a system to translate actual state & desired state into a series of imperative actions, so actual state can be reconciled to desired state. Terraform is a system to translate actual state & desired state into a series of imperative actions, so actual state can be reconciled to desired state. How desired state is expressed can be radically different, and the underlying reconciliation engine can be radically different, but at the end of the day, both tools do the same thing: Executing a Terraform program looks like this: flowchart LR tf["*.tf files"] current["current state"] subgraph engine["reconciliation engine"] direction LR desired["desired state"] --> internal["provider steps"] end output["provider steps"] tf --> desired current --> engine engine --> output Executing a Pulumi program is more dynamic, because the reconciliation engine is in more active dialog with the user's program. That said, the diagram is the same shape. To match semantics, Pulumi HCL dynamically bridges any Terraform provider in the registry. This means that, for the subset of Pulumi programs that are valid OpenTofu programs, both programs take the same input (*.tf files) and produce the same step output (Terraform provider steps). Providers are the part of our model that generates user-observable behavior, which means if we match what providers see, we match what users see. This gives us a really nice definition of correctness for Pulumi HCL1: Pulumi HCL correctly interprets an HCL program when it generates the same set of provider steps as tofu does. If you are familiar with property-based testing, you might be thinking this looks like a testable property. You're right. How we compatibility ## Emulating Terraform on Pulumi's Engine DevFeed: [Emulating Terraform on Pulumi's Engine]() Original publisher: [Read original article]() Author: Ian Wahbe Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Pulumi]() Topics: [Terraform](), [opentofu](), [terraform provider](), [configuration]() Tags: [engineering](), [hcl](), [modules](), [opentofu](), [protocol](), [providers](), [pulumi](), [terraform](), [terraform-provider](), [translation]() ### AI overview This article explains how Pulumi's HCL interpreter maps Terraform configuration, resources, providers, and modules onto the Pulumi engine. It reports that the implementation works with 96% of Pulumi's top Terraform modules and describes how Pulumi's terraform-provider relays between Pulumi and Terraform provider protocols. ### Source excerpt The core promise of Pulumi's HCL support is that you can bring your existing Terraform configuration and modules, and pulumi will run them. If it works in OpenTofu and doesn't work in Pulumi, we would like to fix that. Given that goal, our HCL interpreter needs to take HCL as input and emit instructions to the Pulumi engine that semantically match how tofu would interpret the same input. This is made harder by the fact that Pulumi and OpenTofu have fundamentally different engine semantics and provider ecosystems. This blog post will explore how we have implemented that mapping well enough to get 96%1 of our top Terraform modules working on Pulumi. We'll briefly walk through how Pulumi's HCL interpreter handles Terraform's resource semantics, providers, and modules. It will also call out where Pulumi's HCL support lets you do things that Terraform and OpenTofu will not allow. Providers Both Pulumi and Terraform have providers, but they don't have the same providers. While there are providers that Terraform does not have, Pulumi can always resolve a Terraform provider using Pulumi's confusingly named terraform-provider provider.2 This is the same provider that lets you consume Any Terraform Provider in another Pulumi program with pulumi package add terraform-provider .... The terraform-provider provider acts as a relay: it speaks Pulumi's protocol to the Pulumi engine, and speaks Terraform's provider protocol to the Terraform provider it stands up. Because Pulumi HCL needs to work with all Pulumi providers and because terraform-provider lets Pulumi HCL speak to Terraform providers via the Pulumi protocol, Pulumi HCL actually only speaks Pulumi protocols directly: flowchart LR subgraph n2Entry[" "] n2["terraform-provider"] end subgraph providerBox["Pulumi Provider"] direction TD n2Entry n3["Terraform Provider"] end n0["Pulumi HCL"] <--> n1["Pulumi Engine"] n1 <--> n2Entry n2 <--> n3 n2@{ shape: rect} n3@{ shape: rect} n0@{ shape: rect} n1@{ shape: rect} style n2Entry f ## Keycloak Terraform Provider Release 5 DevFeed: [Keycloak Terraform Provider Release 5]() Original publisher: [Read original article]() Author: Thomas Darimont Published: 2025-01-13T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [terraform provider](), [Keycloak](), [releases](), [Terraform]() Tags: [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [release](), [releases](), [saml](), [sso](), [terraform](), [terraform-provider]() ### AI overview Keycloak Terraform Provider 5.0 was released with support for Keycloak 24 and 26. ### Source excerpt Keycloak Terraform Provider Releases We're excited to announce the release of the Keycloak Terraform Provider 5.0 with support for Keycloak 24/26. You can find the repository here. Following our announcement in December 2024, we released Keycloak Terraform Provider 4.5 with a new license and dependency upgrades for Keycloak versions older than 23.0.0. If you are still using the old Keycloak Terraform Provider by mrparkers you can take a look at the migration notes to use the new Keycloak Terraform Provider. Changes 4.5 Maintenance Release CVE fixes Go upgrade Minor Dependency Upgrades License change 5.0 Release Support for Keycloak 24 Support for Keycloak 26 Dependency Upgrades Planned Next Releases 5.1 with support for managing organizations patch releases on demand Join the Community We're grateful for all contributors who've helped make the Terraform Provider what it is today. We welcome new contributions, issue reports, feature suggestions, and fixes. Let's work together to make it even better! Explore the repository location, join the discussions, and help shape the future of the Keycloak Terraform Provider. ## Keycloak Adopts Terraform Provider DevFeed: [Keycloak Adopts Terraform Provider]() Original publisher: [Read original article]() Author: Thomas Darimont Published: 2024-12-09T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [terraform provider](), [Terraform](), [configuration-management](), [migration](), [releases](), [Go Language]() Tags: [configuration-management](), [cve](), [go](), [idm](), [kerberos](), [keycloak](), [ldap](), [migration](), [openid-connect](), [release](), [releases](), [saml](), [sso](), [terraform](), [terraform-provider]() ### AI overview Keycloak announces that the Keycloak Terraform Provider has moved under the Keycloak organization. The article identifies new maintainers, describes required configuration migration, announces an Apache 2.0 license change, and previews maintenance and 5.0 releases. ### Source excerpt New Repository Location We're excited to announce that the Keycloak Terraform Provider has officially moved under the Keycloak organization! You can find the new repository location here. The Journey So Far Thanks to our community survey, we confirmed that the Keycloak Terraform Provider by mrparkers is the most widely used tool for realm configuration management. The move to the Keycloak organization is a natural next step in making this essential tool a core part of the Keycloak ecosystem. Gratitude and Transition A huge thank-you to mrparkers for creating and maintaining the provider. Your contributions have been invaluable to the community. The new maintainers, Sebastian Schuster and Thomas Darimont, will ensure the project continues to thrive. Migration Notes You'll need to update your configurations to migrate to the Keycloak-hosted Terraform Provider. Check out our migration guide, especially the replace-provider instructions, to make the process smooth. Updates and Changes License Change: The Keycloak Terraform Provider now uses the Apache 2.0 license, ensuring broader adoption and clarity for contributors. Next releases: 4.5 Maintenance Release: Includes CVE fixes, Go upgrade, and license change. 5.0 Release (Upcoming): Adds support for Keycloak 24/26, new features, and improvements. Join the Community We're grateful for all contributors who've helped make the Terraform Provider what it is today. We welcome new contributions, issue reports, feature suggestions, and fixes. Let's work together to make it even better! Explore the new repository location, join the discussions, and help shape the future of the Keycloak Terraform Provider. ## Keycloak Realm Configuration Management Tools Survey Results DevFeed: [Keycloak Realm Configuration Management Tools Survey Results]() Original publisher: [Read original article]() Author: Thomas Darimont Published: 2024-09-11T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [configuration-management](), [terraform provider](), [API](), [Terraform]() Tags: [code-completion](), [configuration-management](), [idm](), [kerberos](), [keycloak](), [ldap](), [management](), [openid-connect](), [realm](), [saml](), [sso](), [terraform](), [terraform-provider](), [validation]() ### AI overview The Keycloak project reports results from a community survey on realm configuration management tools, based on 433 responses. The Terraform Keycloak Provider received about 51% of votes, and the five most-used tools accounted for 84% of responses. Respondents also identified challenges involving Admin API usability, configuration change detection, release compatibility, automatically created components, linting, validation, and code completion. ### Source excerpt Three months ago, the Keycloak project conducted a survey to gather insights on realm configuration tooling within our community. The number of responses overwhelmed us! With a total of 433 (!) submissions, it highlighted the diverse range of options our community uses for configuring realms. Thank You for your valuable feedback! Popular Tools in Use The survey revealed a variety of tools employed by the community for realm configuration, including: Terraform Provider for Keycloak Keycloak-Config-CLI Self-developed Realm Configuration Management Keycloak JSON Import/Export Keycloak Admin CLI kcadm.sh EPAM Keycloak Operator Keycloak Ansible Keycloak Pulumi Custom Operator for Realm Import/Update and Client Provisioning Keycloak Operator Realm Import via Custom Resources Crossplane Provider for Keycloak KeycloakMigration keycloak-configurator Keycloak Groovy Helpers Tool Usage Distribution From the submissions, we observed the following distribution of tool usage among respondents: Terraform Keycloak Provider ~51% of the votes Keycloak-Config-CLI ~16% of the votes Self-developed Realm Configuration Management ~7% of the votes Keycloak JSON Realm Import/Export ~6% of the votes Keycloak Admin CLI ~4% of the votes These top five tools accounted for 84% of all responses. Areas for Improvement While each tool has its strengths and weaknesses, the survey highlighted several common challenges: Using the Admin API can be awkward and inconsistent, for example, with references using IDs versus aliases. Recognizing changes in the configuration, such as when new roles are added to service accounts via the Admin UI, can be challenging or impossible. Many tools depend heavily on the Keycloak version used and are often not compatible with new releases. Managing components that are automatically created by Keycloak, like service accounts, is challenging with existing configuration tools. Lack of support for configuration linting, validation and code completion What's Next? Based on t ## Automating Temporal Cloud with Terraform: Introducing the Terraform Provider DevFeed: [Automating Temporal Cloud with Terraform: Introducing the Terraform Provider]() Original publisher: [Read original article]() Author: Jonathan Lacefield Published: 2024-04-18T04:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [Terraform](), [terraform provider](), [Infrastructure as code](), [Cloud]() Tags: [api-keys](), [authentication](), [cloud](), [infrastructure-as-code](), [product-news](), [terraform](), [terraform-provider]() ### AI overview Temporal announces the public preview of its Terraform Provider, which lets developers manage Temporal Cloud infrastructure as code. The initial release supports automating Namespace and User management, with more resources planned for future updates. ### Source excerpt Automate Temporal Cloud infrastructure with the new Terraform Provider. Manage Namespaces, Users, and certificates using infrastructure as code. ## Exploring Temporal Cloud automation features DevFeed: [Exploring Temporal Cloud automation features]() Original publisher: [Read original article]() Author: Irina Belova Published: 2024-03-25T06:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Automation](), [Cloud](), [terraform provider](), [API](), [Infrastructure as code](), [API keys](), [certificates](), [Security](), [Authentication](), [Command-line interface](), [Kubernetes]() Tags: [api](), [api-keys](), [automation](), [certificates](), [cli](), [cloud](), [infrastructure-as-code](), [mtls](), [organizations](), [platform-teams](), [provisioning](), [security](), [temporal](), [temporal-concepts](), [terraform-provider]() ### AI overview Temporal Cloud's automation features support management of namespaces, users, access, account settings, and team onboarding. The article also describes API, Terraform provider, and Temporal Cloud CLI integrations, including automated mTLS certificate rotation and centralized governance for platform teams. ### Source excerpt Temporal Cloud Automation capabilities are transforming the way companies deploy, manage, and scale their operations in the Cloud. ## Teleport 13 Newsletter DevFeed: [Teleport 13 Newsletter]() Original publisher: [Read original article]() Author: ben@goteleport.com (Ben Arent) Published: 2023-04-15T00:00:00Z Content type: release Language: en Sources: [Teleport]() Topics: [releases](), [Release notes](), [OpenSSH](), [OpenID connect (OIDC)](), [opensearch](), [terraform provider](), [Windows]() Tags: [aws](), [newsletter](), [oidc](), [opensearch](), [openssh](), [release](), [releases](), [terraform-provider](), [updates]() ### AI overview The May 2023 Teleport newsletter summarizes the Teleport 13 release, including automatic agent upgrades, no-code AWS onboarding, TLS routing through an ALB, universal binaries, improved OpenSSH support, Kubernetes tracing, Okta application protection, AWS OpenSearch support, and Windows session recording export. ### Source excerpt Teleport 13 Newsletter - May 2023 Edition