Marko Mikulicic
Marko Mikulicic
Readme says: > NOTE: next release will consolidate this into a single sealedsecrets.bitnami.com/scope annotation. :-) unfortunately it's been a few releases since that promise has been made :-) On the...
I'd like to have this. Contributions are welcome! Small PRs with tests are more likely to be merged quickly :-)
Also, shouldn't we encode the scope in a real field of the SealedSecret resource instead of an annotation?
We still need to have the annotation in the Secret resource though.
The main/historical "UX" for sealed secret is: "Take an existing secret and encrypt it into a SealedSecret" The input for this encryption phase is not limited to the actual secrets,...
Kubeaeal reads the annotation and the flag. If both are set, the flag takes precedence
A lot of people would love to overhaul the CLI but also a lot of people depend on the existing CLI in automation. I believe strongly in backward compatibility and...
> That said, I'm not talking about introducing major changes in the controller side, which should be compatible with both 0.x and the future 1.x series, but exclusively the CLI....
Sounds good to me. As soon as we have feature parity we can start emitting deprecation warnings to stderr. (IMO the 'reasonable period' is very very long, possibly infinite; most...
Implementation-wise, I had a very good experience with github.com/alecthomas/kong as an alternative to cobra