pulumi-kubernetes
pulumi-terraform-bridge
pulumi-kubernetes | pulumi-terraform-bridge | |
---|---|---|
3 | 7 | |
385 | 180 | |
1.6% | 1.1% | |
9.2 | 9.7 | |
1 day ago | 2 days ago | |
Java | Go | |
Apache 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.
pulumi-kubernetes
-
Do not upgrade to pulumi-kubernetes 4.5.0
Still trying to figure out how this slipped through: https://github.com/pulumi/pulumi-kubernetes/issues/2626
-
For IaC: Pulumi or Terraform?
We are working with many cloud providers to have them publish full API specifications so we can generate the schema directly from the upstream source. If you look at our Azure Nextgen it's generated from the published Azure specification. This also means our Azure provider has full coverage of all the Azure resources! The same can be said for our Kubernetes provider
-
Generate Kubernetes YAML with Familiar Programming Languages
While Pulumi has excellent support for deploying and updating Kubernetes resources on a cluster, many users have asked for the option to render YAML that they can integrate into existing workflows. The v1.5.4 release of pulumi-kubernetes adds the renderYamlToDirectory option, which enables this feature. This option is available in every Pulumi-supported language, including TypeScript/JavaScript, Python, and .NET (Go support is coming soon!).
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?
pulumi-aws - An Amazon Web Services (AWS) Pulumi resource package, providing multi-language access to AWS
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
grpc_microservices - This project is a POC of the API Composition Pattern but using gRPC, the idea is having the same proto file implemented in different services (micro or nano) and each service returns a piece of the information to the gateway.
terraform-ls - Terraform Language Server
pulumi-provider-boilerplate - Boilerplate showing how to create a native Pulumi provider
Hacking-Scripts - Hacking Scripts contains amazing and awesome scripts written in Python, JavaScript, Java, Nodejs, and more. The main aim of the repository will be to provide utility scripts that might make everyday life easy.
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-eks - A Pulumi component for easily creating and managing an Amazon EKS Cluster
terraform-provider-spacelift - Terraform provider to interact with Spacelift
aws-cloudformation-res
awesome-cdk - A collection of awesome things related to the AWS Cloud Development Kit (CDK)