pulumi-examples
isopod
pulumi-examples | isopod | |
---|---|---|
9 | 4 | |
46 | 462 | |
- | 0.4% | |
7.0 | 0.0 | |
5 months ago | 6 months ago | |
Python | Go | |
- | 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-examples
- We are the Pulumi Engineering team - Ask us about our new products and features
- Issues trying to extract a buckets arn or id as a str
-
Why are pulumi examples repo not showing good re-useable design patterns
I maintain some examples: https://github.com/jaxxstorm/pulumi-examples
- Deploying Kubernetes clusters in increasingly absurd languages
- Deploying Kubernetes Clusters in Increasingly absurd languages
- Things I Wish I Knew Earlier About Pulumi
isopod
-
Jsonnet – The Data Templating Language
Tried it[0], worked reasonably well. Be prepared for strong opposition from traditional “devops” folks “who don’t mind yaml” and will drag everyone down.
[0] - https://github.com/cruise-automation/isopod
- Deploying Kubernetes clusters in increasingly absurd languages
- YAML: It's Time to Move On
-
Cue: A new language for data validation
I like Cue and Jsonnet and Starlark and so on. But all of these have very low mindshare (though Starlark has the most momentum thanks to Bazel), and who knows if they will be dead by next year.
Being an early adopter is difficult both in terms of the immaturity of the tooling — Cue, for example, only has a Go implementation at the moment — and in terms of the risk of betting on an evolutionary dead end, which can cause a lot of unnecessary churn when you want to standardize on something across an entire organization.
As a concrete example, I'd love to replace Kubernetes's use of YAML with something like the above. But the tooling is immature, and almost nobody is using any of it. For example, there's Isopod [1], which is a nice-looking tool to use Starlark with Kubernetes. But it might go the same way as Ksonnet.
[1] https://github.com/cruise-automation/isopod
What are some alternatives?
examples - Infrastructure, containers, and serverless apps to AWS, Azure, GCP, and Kubernetes... all deployed with Pulumi
skycfg - Skycfg is an extension library for the Starlark language that adds support for constructing Protocol Buffer messages.
civo-production-ready-kubernetes - The repository for the CIVO Navigate talk: How To Build A Production Ready Kubernetes
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
pulumi-terraform - A resource package that allows Pulumi programs to use Terraform state
rules_jsonnet - Jsonnet rules for Bazel
pulumi-aws-native - AWS Native Provider for Pulumi
kubecfg - A tool for managing complex enterprise Kubernetes environments as code.
bfpy - Python to Brainfuck transpiler
c2bf - Compiler from C to brainfuck
ci-mgmt - Configuration for all things CI
jk - Configuration as Code with ECMAScript