Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Could not find property 'stringData' listed in additional secret outputs.

See original GitHub issue

What happened?

Hi, with the latest release (3.34.0 and 3.19.3), the following code:

casc_secrets = kubernetes.core.v1.Secret(
    "casc-secrets",
    metadata={
        "name": "casc-secrets",
        "namespace": core_ns.metadata.name,
    },
    string_data={
        "developer": "developer",
        "browser": "browser",
    },
    opts=ResourceOptions(provider=cluster),
)

Returns:

$ pulumi up
...
     └─ kubernetes:core/v1:Secret  casc-secrets                      1 warning
...
    warning: Could not find property 'stringData' listed in additional secret outputs.

The code works as expected, I am just worried about the warning

Steps to reproduce

$ pulumi up

Expected Behavior

No warning

Actual Behavior

    warning: Could not find property 'stringData' listed in additional secret outputs.

Versions used

$ pulumi about
CLI          
Version      3.34.0
Go Version   go1.17.11
Go Compiler  gc

Plugins
NAME        VERSION
gcp         6.26.0
kubernetes  3.19.3
python      unknown
random      4.7.0

Host     
OS       fedora
Version  36
Arch     x86_64

This project is written in python: executable='/usr/bin/python3' version='3.10.4'

Current Stack: dev-apps-core

TYPE                                                 URN
pulumi:pulumi:Stack                                  urn:pulumi:dev-apps-core::apps-core::pulumi:pulumi:Stack::apps-core-dev-apps-core
pulumi:providers:random                              urn:pulumi:dev-apps-core::apps-core::pulumi:providers:random::default_4_7_0
pulumi:providers:pulumi                              urn:pulumi:dev-apps-core::apps-core::pulumi:providers:pulumi::default
pulumi:pulumi:StackReference                         urn:pulumi:dev-apps-core::apps-core::pulumi:pulumi:StackReference::dev-infra
pulumi:providers:kubernetes                          urn:pulumi:dev-apps-core::apps-core::pulumi:providers:kubernetes::cluster
random:index/randomPassword:RandomPassword           urn:pulumi:dev-apps-core::apps-core::random:index/randomPassword:RandomPassword::core-passwd
kubernetes:core/v1:Namespace                         urn:pulumi:dev-apps-core::apps-core::kubernetes:core/v1:Namespace::core-ns
kubernetes:core/v1:Secret                            urn:pulumi:dev-apps-core::apps-core::kubernetes:core/v1:Secret::casc-secrets
kubernetes:rbac.authorization.k8s.io/v1:Role         urn:pulumi:dev-apps-core::apps-core::kubernetes:rbac.authorization.k8s.io/v1:Role::cjoc-svcmonitors-role
kubernetes:helm.sh/v3:Release                        urn:pulumi:dev-apps-core::apps-core::kubernetes:helm.sh/v3:Release::core
kubernetes:core/v1:ServiceAccount                    urn:pulumi:dev-apps-core::apps-core::kubernetes:core/v1:ServiceAccount::cjoc-sa
kubernetes:rbac.authorization.k8s.io/v1:RoleBinding  urn:pulumi:dev-apps-core::apps-core::kubernetes:rbac.authorization.k8s.io/v1:RoleBinding::cjoc-svcmonitors-rolebinding


Found no pending operations associated with dev-apps-core

Backend        
Name           2453b253f1cb
URL            file:///data/pulumi/.pulumi-local-states/vgervasi-dev-20220609t074734
User           root
Organizations  

Dependencies:
NAME               VERSION
gpg                1.15.1
libcomps           0.1.18
pip                21.3.1
pulumi-gcp         6.26.0
pulumi-kubernetes  3.19.3
pulumi-random      4.7.0
rpm                4.17.0
setuptools         59.6.0

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you’ve opened one already).

Issue Analytics

State:
Created a year ago
Reactions:28
Comments:14 (8 by maintainers)

Top GitHub Comments

8reactions

Frasslecommented, Jun 9, 2022

We’re looking into this but just to allay any worries this is just a diagnostic warning and the behavior of secrets hasn’t changed.

4reactions

viveklakcommented, Jun 16, 2022

I feel the better option is to consider dropping the stringData from outputs for the resource. Its meant to be an input-only utility to avoid having to base64 encode the secret data.

Top Results From Across the Web

Could not find property 'stringData' listed in additional secret ...

What happened? Hi, with the latest release (3.34.0 and 3.19.3), the following code: casc_secrets = kubernetes.core.v1.Secret( "casc-secrets" ...

Create Secret Resource - Pulumi

Documentation for the kubernetes.core/v1.Secret resource with examples, input properties, output properties, lookup functions, and supporting types.

Can't create Secret in Kubernetes: illegal base64 data at input

I got the decoded values "mega_secret_key" and "really_secret_value1" from from your encoded data. Seems they are not encoded in right way.

Providing sensitive data to pods - OpenShift Documentation

Understanding secrets. The Secret object type provides a mechanism to hold sensitive information such as passwords, OpenShift Container Platform client ...

Managing Secrets using Configuration File - Kubernetes

Note: The serialized JSON and YAML values of Secret data are encoded as base64 strings. Newlines are not valid within these strings and...