mfuentesg / ksd Goto Github PK

It appears that bottle :unneeded was deprecated by merging Homebrew/brew#12259. This causes warning messages to be printed:

~ % brew --version
Homebrew 3.3.2
Homebrew/homebrew-core (git revision 4420dde1542; last commit 2021-11-03)
Homebrew/homebrew-cask (git revision e238740ae5; last commit 2021-11-03)
~ % brew doctor
Warning: Calling bottle :unneeded is deprecated! There is no replacement.
Please report this issue to the mfuentesg/tap tap (not Homebrew/brew or Homebrew/core):
  /opt/homebrew/Library/Taps/mfuentesg/homebrew-tap/ksd.rb:6

Your system is ready to brew.

As mentioned in README.md, installed ksd in my local fedora machine but it did not create executable.
Then tried go build in the ~/go/src/mfuentesg/ksd directory which created the executable.
Once created, I ran the below command to fetch the decoded secret.
$ kubectl get secret jx-jx-app-jenkins -o yaml | ~/go/src/github.com/mfuentesg/ksd/ksd

RESULT: Encoded file returned.
Expected Result: Decoded file/ secret.

No where found anything related to this, could someone help me out with this or it's a bug in KSD.

Just a suggestion: when you decode the base64-encoded values under the "data" key, if you replaced "data" with "stringData", the resulting YAML file would be directly usable by kubernetes.

This is useful for situations where you are going to run your YAML through something like sops to allow you to securely store the YAML in git. You want the YAML in a format that is legal for k8s so that when you decrypt from sops, you can feed the results directly to kubectl apply.

Of course, I realize that it's a pretty easy workaround. After running ksd, I can manually edit the YAML to change "data" to "stringData". This is just a small convenience kind of thing.

Closed by #24

It may be appropriate for this project to link to https://github.com/elsesiy/kubectl-view-secret as that tool is offered in krew. Other than this convenience, I have no particular knowledge or opinion of the relative merits, and perhaps there is some justification to offer this in Krew (see ashleyschuett/kubernetes-secret-decode#10 for another tool in this area).

I just ran go get github.com/mfuentesg/ksd about 20 minutes ago (after your 1.0.2 release).

When I pipe a secrets yaml file through ksd, it doesn't modify the base64-encoded data at all. Saving the output to a file and diffing with the original shows no differences between the two.

Hello @mfuentesg ,
Could you show me the ways i can run your test?
Sr for bothering you but I a new comer in Go =))))
Tks in advance!!!