This message was deleted.
# yaml
s
This message was deleted.
b
I think you need to set a key name:
Copy code
data:
       something: ${dockerHubCredentials}
s
yea, that's in the json return. looking to leverage this for secrets that have 20+ key/value pairs. If I drop in the JSON in place of the variable
${dockerHubCredentials}
, it works. The pulumi up return recognizes it as a JSON:
Copy code
Outputs:
    debugDeployment: "stage"
    debugDomain    : "<http://example.com|example.com>"
    debugRegCred   : (json) {
        .dockerconfigjson: "my-base64-encoded-config"
    }

    helmDeploy     : "foo/bar"
    k8s            : "10.10.10.10"
this is a work-around to
kubernetes:yaml:ConfigFile
not being available yet
if I could ingest the raw secrets def, that would work too
(but set the variable from the return of getSecretVersion)
b
I tnink it would be better to remove the
.dockerconfigjson
part from the retrieved secret, and only have it return the secret itself, then you can do
Copy code
.dockerconfigjson: ${dockerHubCredentials}
it’s going to be tricky to manage if you’re trying to split strings and such like in the YAML config
s
eh, was afraid of that. we have hundreds of secrets though across multiple namespaces per deployment. was trying to consolidate this down to 1 config per NS