is there a SST way of automatically exporting environment variables to local

.env

for testing?

We should expand sst-env to facilitate this but I personally avoid this problem by storing everything in

SSM

. Then my application can load it, whether it's a lambda or a test running locally

do you also save userPoolId in

SSM

?

Yeah I do

is it a manual process or you have a way to auto add new item to

SSM

?

new ssm.StringParameter(this, "ParamUserPoolId", {
      parameterName: "/" + this.stage + "/ship/USER_POOL_ID",
      stringValue: pool.userPoolId,
    })
    new ssm.StringParameter(this, "ParamUserPoolClientId", {
      parameterName: "/" + this.stage + "/ship/USER_POOL_CLIENT_ID",
      stringValue: client.userPoolClientId,
    })

Example from my stack code

i see. this looks promising 👍

I pass in SSM_PATH as an env variable into my lambdas. It uses that to with ssm.getParametersByPath to get all config values for the stage

if I understand correctly, you are creating a dedicated SSM stack at the end so that you can store all variables(table, auth)?

I actually am adding the SSM values progressively

sorry one last question - so for testing, you still need to somehow pass the SSM_PATH to tests. How do you manage to accomplish that?

I just pass it with

SSM_PATH=whatever jest

This is a great pattern!

@thdxr I still have trouble accessing SSM from tests. do you mind writing an example I think will benefit the community? 🙏

yeah we have this on our todo haven't gotten to it yet

I am making a call like this:

const result = await ssm.getParametersByPath("/dev/meet-and-donate-app");

and the actual call is:

getParametersByPath: async (path) =>
    SSM.getParametersByPath({
      Path: path,
      Recursive: true,
    }).promise(),

but I am hitting this error:

● Test Stack

    ConfigError: Missing region in config

       7 |       Path: path,
       8 |       Recursive: true,
    >  9 |     }).promise(),
         |        ^
      10 | };

also I am wondering how come our tests can have access to SSM or DynamoDB directly?

Ah you need to pass in

AWS_PROFILE

as an env variable so it uses your local config but also

AWS_SDK_LOAD_CONFIG=1

any thought?

Did passing in those env variables not help?

now it works with

AWS_REGION=‘us-east-1’ SSM_PATH=‘/dev/meet-and-donate-app’ sst test

😇

sweet

does it make sense for SST to pass AWS_REGION as a default env variable?

well, we shouldn't be interfering with the aws-sdk standards. I think AWS_SDK_LOAD_CONFIG would make it read properly from your

~/.aws

config

this also requires

AWS_SDK_LOAD_CONFIG=true

though. https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide/setting-region.html#setting-region-config-file

my region is set in my

~/.aws

config

yeah i just added the region to my

~/.aws/config

but i still have to pass in ``AWS_SDK_LOAD_CONFIG=true` to my test script in order to have the region loaded

yeah that's right - I actually just use

jest

directly not through sst so I was thinking there's nothing sst can do to make that work. I just have it in my package.json

@thdxr I followed your pattern and created my own ssm util methods. It serves my need quite well. I thought it might be useful for the community for future reference: https://gist.github.com/zhuangdaz/68979605ab4e908a71f51051b89d6e61

nice! We have been meaning to write up this pattern