hey <@U01MV4U2EV9>, remember we talked about updat...
# help
s
hey @thdxr, remember we talked about updating the Sentry release hash in SSM, rather than updating in the Lambda envs all the time? how would I do that if we can’t use async funcs in the SST code?
t
You update it with cdk not aws-sdk. Random snippet from my code
Copy code
new ssm.StringParameter(this, "ParamUserPoolId", {
      parameterName: "/" + this.stage + "/USER_POOL_ID",
      stringValue: pool.userPoolId,
    })
Copy code
import * as ssm from "@aws-cdk/aws-ssm"
s
ahhh gotcha! of course
thanks 🙂
any tips on preventing the SSM param from getting destroyed on non-deploys? (since I’m only setting the env var on deploy). other than, of course, having SENTRY_RELEASE in the env for every SST command
Copy code
if (process.env.SENTRY_RELEASE) {
      new ssm.StringParameter(this, 'SentryReleaseHash', {
        parameterName: '/global/sentryRelease',
        stringValue: process.env.SENTRY_RELEASE,
      });
    }