No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

are you saying that it's not triggering an update when hashedPassword changes?

<@U05HLGAFTAA> `hashedPassword` it's bcrypted password, it changed every run.

I have:
```const hashedPassword = bcrypt.hashSync(password, 10);```
I want to trigger secret update only in case of `password` changed, not `hashedPassword`.

Probably there could be a way to save some checksum based on password.

hold up i'm sure i've seen a way to memoize a functional expression, hold up

this can be hacked together using something like random;

```const salt = new random.RandomString("random", {
  length: 22,
  special: false,
  keepers: {
    password
  }
});

const hash = salt.apply(salt => bcrypt.hashSync(password, `$2a$10$${salt}`))```

in this case your hash will always be the same for the same random string

and if i'm not mistaken randomstring will stay the same unless password changes

<@U05HLGAFTAA> Interesting, I will take a look! :slightly_smiling_face: Thanks

you'll have to interpolate the hash into the string;

```import { interpolate } from '@pulumi/pulumi';

...

    stringData: {
      auth: interpolate`${httpUsername}:${hash}`,
    },```

the npm bcrypt library seems to use that semantically, it appends that to the head of the actual random 22 character salt, it could be like a 'salt version' marker

i'm not 100% sure but all salts I created by the npm bcrypt package appear to have it, without it the `hashSync` function fails

<@U05HLGAFTAA> Work like a charm! Thanks

Only `salt.result.apply`.