https://pulumi.com
Join Slack
This message was deleted.
# typescript
s
This message was deleted.
g
are you saying that it's not triggering an update when hashedPassword changes?
p
@gentle-application-59272 
hashedPassword
it's bcrypted password, it changed every run. I have:
Copy code
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.
g
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;
Copy code
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
p
@gentle-application-59272 Interesting, I will take a look! 🙂 Thanks
g
you'll have to interpolate the hash into the string;
Copy code
import { interpolate } from '@pulumi/pulumi';

...

    stringData: {
      auth: interpolate`${httpUsername}:${hash}`,
    },
p
What is 
$2a$10$
?
g
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
👍 1
p
@gentle-application-59272 Work like a charm! Thanks Only 
salt.result.apply
.
✅ 1
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by