Okay, you've moved your infrastructure provisioning from visiting the console page and now adopted IaC ( Infrastructure as Code) for provisioning your infrastructure using Terraform.
So along the way, you discovered that you will need some sensitive credentials like GitHub token to use with aws amplify, datadog API and key deployments?
When you are preparing your vault environment for production, you would want to implement the end-to-end tls setup as stated in the hashicorp vault production-ready documentation.
hello everyone, okay, so I did something recently with GitHub action, re-wrote and optimized a workflow of 900+ lines back to 200+
This is the key-based Cosign post (you manage signing keys). Related:
Hii 👋, I am sure you want peace of mind too, haha
Well, there is no way you would be discussing container supply chain security without talking about the signing of container images.
You are probably handling secrets in Kubernetes like this today:
Yeah, being doing the CI/CD implementations via github workflow lately and I am also trapped in the process of making commits to trigger the workflows or better still making empty commits, haha.
For someone who just started writing Go, I have no idea about //go:embed feature which came with the released version: 1.16.
A project I was working on recently led to discoveries.