having a lot of trouble with pulumi the last few days. pulumi.Ouput({ x: <a pulumi.secret> }) is not resolved in the .apply callback and the CLI is spewing out lines when it tries to render the spinners for

pulumi up

instead of updating the animation in-place anyone else seeing these things?

I haven't seen the 2nd problem. Is the first thing unchanged since it was previously working? Or is it new code that has never done what you want? You could post the code here and we can have a go at diagnosing.

I think it may be an issue with the kubernetes plugin, and how its treating the values prop

Is that in a resource constructor? If not, that is the expected output. I'd need more code to diagnose further

closest thing i have to a isolated test case so far is:

new k8s.helm.v4.Chart(
  'dagster',
  {
    repositoryOpts: {
      repo: '<https://dagster-io.github.io/helm>',
    },
    chart: 'dagster',
    values: {
      postgresql: {
        postgresqlPassword: pulumi.output('test'),
      },
    },
  },
  {
    transforms: [
      args => {
        return args
      },
    ],
  },
)

Yes I'd look at the way that postgresql property is handled. It may well be a simple toString instead of unwrapping and applying.

in a helm chart resource you have the

values

prop which is just a YAML document and shouldn't have any special processing at the pulumi level

Then this behaviour is correct, isn't it?

it was unwrapped prior to the latest version of the kubernetes plugin

There was a change recently that may explain it. Unwrapping nested objects stops at Resource classes now, but it didn't before. So if the values object is implemented in the provider as a resource, that would explain it.

oh boy, im relying on unwrapping nested objects in many many places. e.g.

pulumi.output(deeplyNestedObject).apply(x => JSON.stringify(x))

where can i find more info?

It works for non-resource objects.

am hoping that wrapping the values object like so will work?

values: pulumi.output({ ... })

Yes. So long as the object's class isn't Resource, then you should be good. If not, then raise an issue.

im looking through the changelog and can't seem to find any info about this new unwrapping behaviour. would you happen to have a link handy?

I saw the link in Slack about 10 days ago maybe? Pretty sure I was in the thread, I'll check my history.

ok here is my repro code:

import * as pulumi from '@pulumi/pulumi'
import * as k8s from '@pulumi/kubernetes'
import * as random from '@pulumi/random'

const uc = {
  env: 'bug'
}

const psql = (() => {
  const host = `dagster-postgresql.dagster-${uc.env}`
  const user = 'dagstersu'
  const rnd = new random.RandomBytes('sasl-password', { length: 32 })
  const pass = pulumi.interpolate`dagster_${rnd.hex}`
  const db = 'dagster'
  return { host, user, pass, db }
})()

new k8s.helm.v4.Chart(
  'dagster',
  {
    repositoryOpts: {
      repo: '<https://dagster-io.github.io/helm>',
    },
    chart: 'dagster',
    values: {
      postgresql: {
        postgresqlHost: psql.host,
        postgresqlUsername: psql.user,
        postgresqlPassword: psql.pass,
        postgresqlDatabase: psql.db,
      },
    }
  },
  {
    transforms: [
      args => {
        console.log(args.props.values.postgresql)
        return args
      }
    ]
  }
)

Is the function needed? Does the issue happen if you replace that with a simple object?

things that make the bug go away: • dropping the transform function (i need it for other reasons) • using a static string for

postgresqlPassword

• using any other type of pulumi.output for password, it seems to be if specifically from Random that it causes this bug