budimanjojo/talhelper v1.4.0

on GitHub

Notice

You can now put a talsecret.yaml file and talhelper will use that
file to generate config for you. The old behaviour of using
talenv.yaml will still be supported, but I think talenv.yaml is more
of for variable substitution while talsecret.yaml is for cluster
secret tokens and keys (it can only be used for that too).

You can migrate to the new talsecret.yaml like this:

1. talhelper gen secret --from-configfile ./clusterconfig/mynode.yaml > talsecret.yaml
2. Encrypt talsecret.yaml with SOPS.
3. Remove all the inlinePatch created by gensecret --patch-configfile flag
4. Optionally delete the talenv.yaml file.

Changelog

• 1e3d313 Merge pull request #28 from budimanjojo/renovate/renovatebot-github-action-32.x
• 08ac990 Merge pull request #29 from budimanjojo/next
• 7e75a37 feat!(gensecret): different gensecret output and flag deprecation
• 37bb355 feat(code): fix golanglint error
• 03916e4 feat(genconfig): can generate config using talsecret.yaml
• 70a8942 feat(genconfig): don't forget to remove the file
• 3e39109 fix(code): fix golanglint error