terraform-plugin-sdk
pulumi-terraform-bridge
terraform-plugin-sdk | pulumi-terraform-bridge | |
---|---|---|
7 | 7 | |
417 | 180 | |
1.2% | 1.1% | |
8.8 | 9.7 | |
3 days ago | 4 days ago | |
Go | Go | |
Mozilla Public License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-plugin-sdk
-
Part 4 - Terraform Providers
Reference : Plugin Development url references
-
Converting Full Terraform Programs to Pulumi
> We're coming up on 10000 resources in our main Terraform repository and while there is definitely some friction, it's overall much better than having to hit the cloud API's to gather each of those states which would probably take at least an order of magnitude longer.
I don't think that's necessary true. Most cloud API's actually can return hundreds of records with 1 API calls, e.g. https://docs.aws.amazon.com/elasticloadbalancing/latest/APIR... has a maximum page size of 400.
If I manage the cloud resources via some custom tools and/or with some ansible-fu, I can decide to batch the API calls when it makes sense.
With terraform, it is not possible to do so (https://github.com/hashicorp/terraform-plugin-sdk/issues/66, https://github.com/hashicorp/terraform-provider-aws/issues/2...).
-
Terraform "bug" / Azure "feature"
While it would be nice for Terraform to find duplicate resource blocks prior to the apply, it's impossible for it to do this without knowledge of the underlying provider being used. As an example, in AWS you could have multiple aws_instance resource blocks with identical attributes and it would be a perfectly acceptable situation (you'd probably be better off with an ASG, but I digress). The real issue here is that the Azure API is not returning an error when the duplicate resource group is being created. The parent feature request mentions other situations, some resulting in errors (preferred/acceptable), others resulting in duplicate resources. However, none are as potentially dangerous as a resource group since it can contain any number of other resources.
-
Maintaining the terraform provider for docker
Currently, we are working on an internal refactoring to clean up code from the past years, even before we started the maintainership. Due to the upgrade to terraform-sdk-v2, we have new abilities for logging, debugging, and testing in isolation. Also, tools for the generation of documentation will simplify the process and keep it up-to-date. But first of all, we want to fix the reported bugs and clarify if they are still present after the update. We also plan to add support for running docker behind a jump host and provision docker containers. Our most aspiring goal is to come close to the docker CLI as possible. To achieve this, we plan to review which code we can reuse and integrate. For example, this has already been happened in the past to allow the converging possibility for docker services. We plan to add the generation of the changelog as we enforce already conventional commits from angular. After talking about the path towards milestone 3.0, we wrap it up with the conclusion.
-
Panic Interface Conversion (Int64)
Thank you for pointing that out u/tgulacsi I changed the type to Int and the panic issue was resolved; however, preferably I would like to use what the API definition states which is int64, but if I understood correctly, there is no native way of doing without conversion according to this GitHub Issue, which seems to be more of Terraform limitation than anything.
-
Root resource was present but now absent
This particular situation is interesting because I can't think of any situation where it would be valid for Create to return a real null without also indicating an error, and so in theory the SDK itself could catch that situation and report it to you using SDK terminology instead, perhaps even directing you to make sure you called d.SetId. It could be worth sharing this experience as an issue in the Terraform SDK repository so that the team which works on the SDK can consider whether it's possible for the SDK to give you better feedback in this situation, rather than just returning the invalid result to Terraform Core to check.
-
Polymorphic resources: provider best practices
I did some more work on this and it seems [1] is the way to go, because it indeed prevents an explosion of resources (and as a result lots of duplication in the documentation). Secondly, there are explicit provisions in the terraform plugin SDK to handle sets of fields which are conflicting with others, so mistakes are handled even at terraform init.
pulumi-terraform-bridge
-
We are the Pulumi Engineering team - Ask us about our new products and features
GA: automatic token mapping and aliasing in the bridge, which we're now using to simplify the resources.go file in bridged providers
-
Converting Full Terraform Programs to Pulumi
Yes, pulumi is just wrapping terraform[1]. So you need to understand both the quirks of that and the quirks of pulumi. And I'm lazy so I just want to deal with one quirk at the time.
[1] https://github.com/pulumi/pulumi-terraform-bridge
-
Weird warning after running pulumi preview
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
-
CDKTF
They have an open source tool that translates the TF providers into Pulumi providers, so people could continue to build updated providers - https://github.com/pulumi/pulumi-terraform-bridge
-
Terraform 1.0 Release
> If Pulumi didn't bless it, it doesn't exist in Pulumi's world.
That has not been my experience. I have personally ported a Sentry TF provider into Pulumi, and I will grant you that their docs and examples are bordering on active user hatred for exercising the process, but it does work:
https://github.com/pulumi/pulumi-terraform-bridge#adapting-a...
https://github.com/pulumi/pulumi-tf-provider-boilerplate#rea...
What mystifies me about that situation is that I do actually appreciate the amount of silliness that is required to avoid using Pulumi cloud: they are not financially incentivized to make that easy, but I'd guess a lot more folks would nope right out if they didn't make it possible
However, I would think they'd want to make ingesting a TF provider into Pulumi as smooth and reliable as possible, so they don't have people close their browser tab when they don't find a supported provider for Pulumi but it exists in TF
-
Is AWS Cloud Development Kit (CDK) right for you?
For provisioning infrastructure in AWS, there are other tools besides those provided by AWS themselves. This includes Terraform and Pulumi. Both of these are not tied to any particular public cloud provider, or not even to public cloud providers only. Any kind of Software-as-a-service (SaaS) provider that can provide some service or infrastructure via programming interfaces can in theory be provisioned by these tools. Terraform has a long list of providers, and Pulumi can use Terraform providers in addition to its providers.
-
For IaC: Pulumi or Terraform?
I think they might use their (pulumi-terraform-bridge)[https://github.com/pulumi/pulumi-terraform-bridge] to generate some of their provider code from the corresponding Terraform providers? (This page mentioned some of their "most interesting providers" are created like this)[https://www.pulumi.com/docs/intro/vs/terraform/#using-terraform-providers].
What are some alternatives?
grpc-production-go - A gRPC production-ready library
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
prototool - Your Swiss Army Knife for Protocol Buffers
terraform-ls - Terraform Language Server
git-chglog - CHANGELOG generator implemented in Go (Golang).
pulumi-provider-boilerplate - Boilerplate showing how to create a native Pulumi provider
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
porter - Porter enables you to package your application artifact, client tools, configuration and deployment logic together as an installer that you can distribute, and install with a single command.
pulumi-aws - An Amazon Web Services (AWS) Pulumi resource package, providing multi-language access to AWS
terraform-provider-spacelift - Terraform provider to interact with Spacelift
pkisauce - Ephemeral One Time/Build-Time gRPC TLS PKI system.
aws-cloudformation-res