sls-lambda-opa
pulumi-aws
Our great sponsors
| sls-lambda-opa | pulumi-aws | |
|---|---|---|
| - | 3 | |
| 52 | 417 | |
| - | 3.4% | |
| 0.0 | 9.5 | |
| over 2 years ago | 9 days ago | |
| Go | 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.
sls-lambda-opa
We haven't tracked posts mentioning sls-lambda-opa yet.
Tracking mentions began in Dec 2020.
pulumi-aws
-
HashiCorp Adopts Business Source License
Sure, but the providers for some of the biggest platforms are maintained by HashiCorp[1] - like the AWS, Azure, GCP, and Kubernetes providers[2], and it appears the Pulumi AWS provider (for example) _does_ use the Terraform AWS provider, even to this day[3].
1. https://developer.hashicorp.com/terraform/registry/providers... - "official" providers are maintained by HashiCorp
2. https://registry.terraform.io/browse/providers?tier=official - The filtered list of "official" providers maintained by HashiCorp
3. https://github.com/pulumi/pulumi-aws/tree/008c4360bc9fc24303... - Just prove it to myself, I can see the `upstream` git submodule, which embeds pulumi/terraform-provider-aws, which is a fork of hashicorp/terraform-provider-aws, although the repo was not created as a fork in Github, so it is not marked as a "fork" and so I have to compare commit histories to tell that it is a fork.
-
Converting Full Terraform Programs to Pulumi
>Isn't pulumi aws just terraform under the hood still?
It depends.
The AWS "Classic" provider uses the terraform provider [1].
The AWS "Native" provider does not, and instead uses the AWS Cloud Control API [2].
[1]: https://github.com/pulumi/pulumi-aws
[2]: https://github.com/pulumi/pulumi-aws-native
-
For IaC: Pulumi or Terraform?
Pulumi uses terraform providers to schematize the CRUD options for some cloud providers. Part of the difficulty with any infrastructure as code offering is that your favourite cloud provider doesn't always provide a full API spec, so we need to somehow figure out what resources can be created, what parameters are available to those resources etc. We take the terraform provider, look at the available operations for that provider and then turned it into a Pulumi schema, which can then be read by the Pulumi engine. If you take a look here you can actually see that generated schema for AWS.
What are some alternatives?
go-localstack - Go Wrapper for using localstack
terracognita - Reads from existing public and private cloud providers (reverse Terraform) and generates your infrastructure as code on Terraform configuration
doctl - The official command line interface for the DigitalOcean API.
humbug - Get usage metrics and crash reports for your API, library, or command line tool.
pulumi-kubernetes - A Pulumi resource provider for Kubernetes to manage API resources and workloads in running clusters
pulumi-eks - A Pulumi component for easily creating and managing an Amazon EKS Cluster
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
EBS-Optimizer - Source code of the initial version of the EBS Optimizer tool made available on the AWS Marketplace.
terraform-plugin-sdk - Terraform Plugin SDK enables building plugins (providers) to manage any service providers or custom in-house solutions
pulumi-terraform-bridge - A library allowing providers built with the Terraform Plugin SDK to be bridged into Pulumi.
awesome-go-with-stars - Awesome-go list with stars. Automatically updated.
Percona Server - Percona Server