Our great sponsors
-
pulumi-terraform-bridge
A library allowing providers built with the Terraform Plugin SDK to be bridged into Pulumi.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
After digging, I saw python libraries in my venv directory that is related to Terraform Bridge and the tool that was used to generate code - https://github.com/pulumi/pulumi-terraform-bridge
The reason you see that is because the AWS Classic provider (pulumi_aws) is built on top of the open-source terraform-provider-aws (via the Terraform bridge you identified), and terraform-provider-aws is emitting that notice at runtime. Not all Pulumi providers are built from Terraform providers, however, but some, like this one, still are. (There's a notice at the bottom of the page for each resource where this is the case.) It works like this:
Related posts
- How To Manage Amazon GuardDuty in AWS Organizations Using Terraform
- AWS EKS: From IRSA to Pod Identity With Terraform
- AWS Makes Cloud Formation Stack Creation Up to 40% Faster
- Authorization and Amazon Verified Permissions - A New Way to Manage Permissions Part XII: Terraform
- obsidian terraform code support (hcl)