Kris Nóva
Kris Nóva
This is critical, if a user nukes their state store accidentally (which I have totally done), this will give us the ability to get it back to another version.. Furthermore...
Right now dep was trying to find versions for a bmi if it was a root level package.. This PR bypasses the BMI in this case so we don't fail...
https://github.com/hairyhenderson/gomplate
See https://pkg.go.dev/k8s.io/cli-runtime
Relevant to #61 we can harden our package management We can (and should) use reflection to snoop the Kubernetes libraries as needed. We need to get rid of the string...
Right now we have a problem with vendoring and capturing the compile commands with naml We can use `naml build` as a way to vet the code and ensure everything...
with merging #67 we introduce some new paradigms - You can pass `nil` as a kube client to `Install(client)` and `Uninstall(client)` - There is a new interface method `Objects() []runtime.Object`...
🎉 now that we are writing Go like professional business grown-ups we can do controllers and CRD beeps and boops
ideally our applications would be immutable in nature after `New()` is called we should come up with some examples of how to do this
## [unhide(8)](https://linux.die.net/man/8/unhide) man page See possible vectors for discovering hidden PIDs in [unhide(8) tests](https://man.archlinux.org/man/community/unhide/unhide.8.en#TEST_LIST)