office-booker
pulumi-tf-provider-boilerplate
| office-booker | pulumi-tf-provider-boilerplate | |
|---|---|---|
| 3 | 3 | |
| 38 | 68 | |
| - | - | |
| 0.0 | 6.1 | |
| over 1 year ago | 14 days ago | |
| TypeScript | Go | |
| MIT License | 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.
office-booker
-
We are the Pulumi Engineering team - Ask us about our new products and features
Here's a non-trivial example: https://github.com/o2Labs/office-booker
-
Can anyone recommend some production quality fullstack TS repos on Github?
Front end, back end and AWS infrastructure all written in Typescript https://github.com/o2Labs/office-booker
- Any good example open-sourced large CRUD backend applications I can look at for reference on code structure, design patterns, etc
pulumi-tf-provider-boilerplate
-
We are the Pulumi Engineering team - Ask us about our new products and features
I'm interested in how to take existing high-quality Terraform Providers and convert them into Pulumi providers. Can you discuss the future roadmap for this project and any others around this effort.
-
What's missing in Pulumi?
The documentation on https://github.com/pulumi/pulumi-tf-provider-boilerplate would benefit from more examples and further explanation. I had to reverse engineer the pulumi-aws provider to be able to wrap an existing TF provider.
-
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
What are some alternatives?
civo-production-ready-kubernetes - The repository for the CIVO Navigate talk: How To Build A Production Ready Kubernetes
booster - Software development framework specialized in building highly scalable microservices with CQRS and Event-Sourcing. It uses the semantics of the code to build a fully working GraphQL API that supports real-time subscriptions.
aws-cloudformation-resource-providers-rds - The CloudFormation Resource Provider Package For Amazon Relational Database Service
pulumi-aws-native - AWS Native Provider for Pulumi
redux - A JS library for predictable global state management
terraform-lsp - Language Server Protocol for Terraform
pulumi-examples
cnab-spec - Cloud Native Application Bundle Specification
pulumi-terraform-bridge - A library allowing providers built with the Terraform Plugin SDK to be bridged into Pulumi.
terraform-ls - Terraform Language Server