Secret namespace does not work for non-default value

[stephenchu]

Using this repo's secret_example.yml, when I pass --secret webapp default, it renders correctly:

› git clone https://github.com/InQuicker/ktmpl.git bug && cd bug
...

› docker pull inquicker/ktmpl:latest
latest: Pulling from inquicker/ktmpl
Digest: sha256:02eb1cc8274f114c9284a3e02a6d7831f30cdc82893723486c6a3ca9e7532f32
Status: Image is up to date for inquicker/ktmpl:latest

› docker run --rm \
  -v $(pwd):/work \
  -w /work \
  inquicker/ktmpl:latest \
  --parameter PASSWORD pass \
  --secret webapp default \
  secret_example.yml

---
apiVersion: v1
data:
  config.yml: "dXNlcm5hbWU6ICJjYXJsIgpwYXNzd29yZDogInBhc3MiCg=="
kind: Secret
metadata:
  name: webapp
type: Opaque

However, when I alter the secret namespace from default to default1, it no longer renders:

› docker run --rm \
  -v $(pwd):/work \
  -w /work \
  inquicker/ktmpl:latest \
  --parameter PASSWORD pass \
  --secret webapp default1 \
  secret_example.yml
Error: Not all secrets specified were found.

/cc @jimmycuadra: I can't log issues to your forked branch, so I am creating it here instead.

[jimmycuadra]

Sorry about the issues! I don't know why they were disabled on my fork, but I've now enabled them in case you run into issues in the future.

Regarding this issue, I think you've misunderstood what the namespace parameter is for. It doesn't allow you to override a default, it's used for specifying which secret you're referring to, because it's possible to have secrets with the same name but in different namespaces.

I don't have access to this repo anymore, so please close the issue if it's solved for you. Thanks!