sprig
sops
Our great sponsors
sprig | sops | |
---|---|---|
11 | 150 | |
3,985 | 15,114 | |
1.8% | 2.7% | |
0.0 | 9.0 | |
2 months ago | 3 days ago | |
Go | Go | |
MIT License | Mozilla Public 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.
sprig
-
Templ: A language for writing HTML user interfaces in Go
Standard Go templating seems really lacking if you come from something like Jinja. Even with libraries like https://masterminds.github.io/sprig/ (used e.g. for Helm templating) it feels hard to use.
-
Improve performance of Go serving a React frontend
Eleven, you'd be surprised what go template libs are out there like sprig. https://masterminds.github.io/sprig/
-
What would you choose if you are in my shoes?
If you use Go templates be sure to use Sprig as well to get more usable functions.
-
Library to convert HTML to pdf in Golang
I'd highly recommend tossing in the sprig library and depending on how you break up your templates, maybe creating a custom "include" helper instead of using the built in define/template helpers. The advantage of this is that if each template is capable of rendering itself independently, you can potentially render all of your templates in parallel.
-
Jsonnet – The Data Templating Language
The discoverability of golang templates is terrible, IMHO, since it's missing a "dir(locals())" equivalent and every execution environment gets to make its own rules about what pipelines/functions are exposed
Look at helm as an example: https://helm.sh/docs/chart_template_guide/function_list/ is some of them, https://helm.sh/docs/chart_template_guide/accessing_files/#p... are some others, but they also glued in some version of https://masterminds.github.io/sprig/ So, short of (a) knowing that's the case (b) having 3+ bookmarks in your favorite browser to refer to those reference pages, how would anyone know what pipelines are available?
Separately, I dooooo nooooooot understand why every joker has to invent their own new thing when we have like 50 or so templating languages already. Golang may be an outlier in that competition due to the Google Promotion Packet Effect(tm) but how they came up with `{{ range }}{{ end }}` as sane syntax is some true facepalm, to say nothing of the same landmine that ansible stepped on by not switching jinja2's default characters: `{{` is not _yaml safe_
-
Charm: a new language in, with, and for Go
You mentioned something about PHP. We also already have a templating language in the standard library that can be extended (commonly done with sprig).
-
Is there something similar to plopjs in Go? (generate files based on configuration from templates)
Plopjs looks interesting and is probably not too hard to write for yourself in Go. You could add something like sprig for some useful template functions.
-
Tips for running "good" coding interviews?
Not at all. It was "write a helm template using the following imaginary values in a values file". In 30 minutes, I was able to google the Kubernetes api and the sprig functions for templating, complete the assignment, fix a stupid typo the unit test caught, and spend 5 minutes trying to think of any corner cases that hidden unit tests might catch (I don't know if there were any hidden unit tests). The goal of this take-home assessment was to prove that you are not wasting an engineer's time when they call you, not to prove that you should be hired.
-
tfcmt - Improve Terraform Workflow with PR Comment and Label
Support sprig in Template
-
Kyoto – Build Front End with Golang
They may refer to the definitive shortage of built-in functions. The template engine itself only provides the bare minimum. That's usually not a problem because of template function libraries like https://github.com/Masterminds/sprig
sops
-
Pico.sh – Hacker Labs
My script just sets up default .sops.yaml for https://github.com/getsops/sops
You can further edit .sops.yaml(eg have multiple of them) and decide how you split secrets in your directory tree to further customize who can decrypt the secrets.
It works pretty well for prod/dev splits, etc
-
Encrypting your secrets with Mozilla SOPS using two AWS KMS Keys
Mozilla SOPS (Secrets OPerationS) is an open-source command-line tool for managing and storing secrets. It uses secure encryption methods to encrypt secrets at rest and decrypt them at runtime. SOPS supports a variety of key management systems, including AWS KMS, GCP KMS, Azure Key Vault, and PGP. It's particularly useful in a DevOps context where sensitive data like API keys, passwords, or certificates need to be securely managed and seamlessly integrated into application workflows.
-
An opinionated template for deploying a single k3s cluster with Ansible backed by Flux, SOPS, GitHub Actions, Renovate, Cilium, Cloudflare and more!
Encrypted secrets thanks to SOPS and Age
-
Tracking SQLite Database Changes in Git
We do the exact same thing to keep track of some credentials we use sops[1] and AWS KMS to separate credentials by sensitivity, then use the git differ to view the diffs between the encrypted secrets
Definitely not best practice security-wise, but it works well
[1] https://github.com/getsops/sops
-
The Twelve-Factor App
For anyone new to SOPS like I was - https://github.com/getsops/sops
- Storing and managing private keys
-
Show HN: Shello – Wrangle Environment Variables
I've found this is largely solved by strictly separating plain config and secrets, and then having secrets pull from GCP secret manager / vault / whatever.
You can then commit all the config (including the secret identifiers) and it all just works so long as you're authenticated with your secret storage system.
We do this for the live configuration as well in line with Gitops and find it to work well.
If you don't want to use a cloud secret manager you can also use something like https://github.com/getsops/sops to commit the encrypted secrets safely
-
Check your secrets into Git [video]
Basically, the simpler the better --just encrypt your secrets and check them in to version control.
We use SOPS[0] for this, and have found it to be pretty nice.
[0]: https://github.com/getsops/sops
-
How to secure secrets of docker-compose stacks with git?
The answer is that secrets shouldn't be stored in the git repo at all, but somewhere safe like a password manager or Mozilla's SOPS which people seem to love.
-
Is it safe to commit a Terraform file to GitHub?
Unfortunately, the SOPS project is in some sort of a limbo state and there has been quite a long period with limited maintenance and unclear position from Mozilla. Despite the project being accepted into the CNCF, it's still unclear what will happen with it going forward.
What are some alternatives?
pongo2 - Django-syntax like template-engine for Go
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
Jet Template Engine for GO - Jet template engine
Vault - A tool for secrets management, encryption as a service, and privileged access management
liquid - A Liquid template engine in Go
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
Plush - The powerful template system that Go needs
git-crypt - Transparent file encryption in git
fasttemplate - Simple and fast template engine for Go
terraform-provider-sops - A Terraform provider for reading Mozilla sops files
amber - Amber is an elegant templating engine for Go Programming Language, inspired from HAML and Jade
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.