troposphere
dhall-kubernetes
Our great sponsors
troposphere | dhall-kubernetes | |
---|---|---|
17 | 9 | |
4,900 | 608 | |
0.2% | 0.3% | |
9.0 | 4.2 | |
1 day ago | 4 months ago | |
Python | Dhall | |
BSD 2-clause "Simplified" 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.
troposphere
-
AWS Predictions for 2024
Under the IaC category, in July 2023, AWS added loops to CloudFormation, finally ticking a box the community has been asking for since troposphere. I suspect that, in combination with the Terraform licensing changes, it may keep people using CloudFormation for a while longer.
-
Journey of creating a new AWS CloudFormation resource
Because ECS Compose-X uses Troposphere, I was able to create a very light and simple python library(https://github.com/JohnPreston/troposphere-awscommunity-applicationautoscaling-scheduledaction) to distribute the resource for other Troposphere users to re-use.
- What are some of your favorite projects to support on GitHub?
-
Terraform vs. Cloudformation for an all-AWS Environment in 2023?
Written in house, but the library troposphere is the primary component of how it is built. Example stacks are here.
-
How proficient should Solution Architects be at writing code?
I am kind of going off topic here, but isn't the point of being an SA to be created with code services to deliver solutions at scale that are cost-effective? How in the hell can you do that when you can't write a simple Python template that generates code at 50 times the rate you can manually? How can you ever be expected to deploy a serverless solution if you can't write any code yourself? There has to be some level of proficiency there.
-
Terraform should have remained stateless
Wouldn't using troposphere[1] be easier?
-
Hosting your blog on AWS
You might have seen some tutorials on how to set up S3 buckets using the AWS Console. This works fine, but I'm a firm believer of managing your resources with code. I've chosen the native solution of AWS, called AWS CloudFormation. This makes it easier to reproduce the setup if I ever need to tear it down of move it to another account or region. Below is the full CloudFormation template, I've used a framework called Troposphere, a Python library that creates CloudFormation.
-
Alert: Cloud Software Startup Hashicorp Files For IPO
For CF for example I no longer write template in yaml or shudders json, and instead I use troposphere.
-
AWS pros out here, how can someone get good at CloudFormation ?
refer : https://github.com/cloudtools/troposphere
- Troposphere – A Python library which allows you build cloudformation templates
dhall-kubernetes
-
DSLs Are a Waste of Time
I hate yaml with a passion. It marginally better than xml for reading (wins huge on comment syntax) and worse for everything else. It makes zero sense we somehow ended up with it as standard configuration serialization format.
Note yaml is not a DSL. It's a tree serialization format! Everything interesting is happening after it is parsed. Extreme examples point to e.g. github actions conditions.
Anyway, back on topic - maybe not prolog for CDK, but still quite interesting: Dhall-kubernetes - https://github.com/dhall-lang/dhall-kubernetes
-
Why is Kubernetes adoption so hard?
At this point, if it’s painful enough, why isn’t compiling-to-yml tools more popular?
Example: https://github.com/dhall-lang/dhall-kubernetes
Haven’t used dhall myself but I’d definitely prefer a DSL on top of yaml.
-
Nyarna: A structured data authoring language in the spirit of LaTeX, implemented in Zig
Dhall provides https://github.com/dhall-lang/dhall-kubernetes which is exactly this: statically type-checked kubernetes config generation.
-
The Dhall Configuration Language
Dhall is my favorite configuration language that I never get around to using.
I manage DNS in Terraform, and since every Terraform provider uses different objects definitions, and every object definition is rather verbose, Dhall would be a way to specify my own DRY types and leave the provider-specific details in one place. Adding new DNS entries and moving several domains between providers would be a matter of changing fewer lines.
Dhall also has Kubernetes bindings:
https://github.com/dhall-lang/dhall-kubernetes
Although I'm tempted to just stick to Helm here, even though it's less type-safe.
-
Why helm doesn't use a general purpose programming language for defining resources?
Not Helm directly, but does something like Dhall fit your question? https://github.com/dhall-lang/dhall-kubernetes
-
Dhall configuration language as another way to write manifests for Kubernetes
Have you heard about Dhall? It’s a programming language used for generating configuration files for a variety of purposes. One of them is to replace old and limited formats such as JSON and YAML. It is DRYable, secure, and even suitable for creating K8s manifests. The latter option isn’t something for anyone: you have to learn a new language and deal with its peculiarities, but it might be really helpful when you have tons of YAML configs. I’ve recently made a short intro to Dhall for K8s in this review.
-
Terraform 1.0 Release
Best thing is Dhall that I am aware of. Same situation, working as a consultant, forced to use broken things.
-
Write Gitlab CI Pipelines in Python Code
Lets look at a specific example. Take Kubernetes: everything is yaml, with complete schemas, all the way down. From your perspective this is configuration utopia, right? Meanwhile back in reality k8s is the poster child of "yaml hell". From the day it was released, people took one look at it, gave it a giant NOPE and instantly spawned half a dozen templating languages. The most popular of these is helm, which has a terrible, no good, very bad design: full of potential injection attacks from purely textual string substitution, manually specified indentation to embed parameterized blocks, virtually no intermediate validation, no way to validate unused features, etc etc
Compare to dhall which publishes a complete set of dhall-k8s schema mappings which enables you to factor out any design you want down to as few configuration variables as you like, while validating the configuration generators themselves at design time. https://github.com/dhall-lang/dhall-kubernetes#more-modular-...
-
INTERCAL, YAML, And Other Horrible Programming Languages
The solution I like is Dhall. They even have a Kubernetes solution that will catch a lot of issues at compile-time, before you try to apply it to Kubernetes. At earthly we aren't actually using it though. Our Kubernetes guru found it to be a bit slow but I am hopeful it or something like it will be the future.
What are some alternatives?
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.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
aws-cloudformation-coverage-roadmap - The AWS CloudFormation Public Coverage Roadmap
nvim-lspconfig - Quickstart configs for Nvim LSP
gohugo-theme-ananke - Ananke: A theme for Hugo Sites
starlark - Starlark Language
aws-cli - Universal Command Line Interface for Amazon Web Services
NUKE - 🏗 The AKEless Build System for C#/.NET
gitlab-ci-python-library
vim-lsp - async language server protocol plugin for vim and neovim
www-gitlab-com
tanka - Flexible, reusable and concise configuration for Kubernetes