Write Keptn Tasks: Secret text is misleading

[agardnerIT]

Kubernetes secrets can also be passed to the function using the secureParameters field. Here, the secret value is the K8s secret name that will be mounted into the runtime and made available to the function via the environment variable SECURE_DATA.

This leads me to believe I can do:

kubectl -n default create secret generic test-secret \
--from-literal=foo=bar \
--from-literal=foo2=bar2

apiVersion: lifecycle.keptn.sh/v1alpha2
kind: KeptnTaskDefinition
metadata:
  name: dummy-task
  namespace: "default"
spec:
  function:
    secureParameters:
      secret: test-secret
    inline:
      code: |
		let secret_values = Deno.env.get('SECURE_DATA');
                // Somehow get `foo` and `bar` from `secret_values`

But I cannot. In reality, my secret must take a certain form with SECURE_DATA as the key:

kubectl -n default create secret generic test-secret \
--from-literal=SECURE_DATA=foo

Which is fine, but then:

a) Keptn is forcing me to change the way I handle secrets
b) I need 2 secrets now, not one

For b) I cannot reference multiple secrets in a KeptnTaskDefinition. The following is not possible:

# assume 2x secrets: foo-secret and bar-secret exist

apiVersion: lifecycle.keptn.sh/v1alpha2
kind: KeptnTaskDefinition
metadata:
  name: dummy-task
  namespace: "default"
spec:
  function:
    secureParameters:
      secret: foo-secret
      secret2: bar-secret

So I try to use a file:

# secret_file.json
# {
#    "foo": "bar",
#    "foo2": "bar2"
# }

kubectl -n default create secret generic file-secret --from-file ~/temp/secret_file.json

Yet I still get the SECURE_DATA error.

[agardnerIT]

Please assign to me. I will work on this.

[agardnerIT]

#781 closes this. It has been merged and I can see it in the (currently upcoming) 0.6.0 release so I will close this: #592