https://serverless-stack.com/ logo
Join Slack
Powered by
Hey all, another issue after upadting and we are k...
# help
r
Hey all, another issue after upadting and we are kinda stuck here. It seems that non of the environmental variables are making it into our local dev. Whether its something like this
Copy code
app.setDefaultFunctionProps({
    // environment: {
    //   NODE_OPTIONS: '--enable-source-maps',
    // },
or this for an Api
Copy code
environment: {
          USER_TABLE_NAME: userTable.tableName,
          CACHE_TABLE_NAME: cacheTable.tableName,
        },
They always seem to be missing... Any ideas?
hey @thdxr hate to ping ya, but definitely stuck on this one. Not able to share anything right now as all our table name ENVs are missing. any idea what could have effected this?
t
when you look in the aws console
are they in there?
r
yes they are
but if i log process.env they are not there
t
this is bizarre, I have it working locally
r
yes i am not sure what is different here. i trashed my 
node_modules
just incase
t
can you send me your .build/sst-debug.log
when you log process.env do you see 
IS_LOCAL
r
yes i do. 1 sec ill get ya a log
I went back to a basic example and got some envs, so I am going back to the more complicated setup and trying again. hopefully its just something dumb i am doing.
Welp I have no idea what got mixed up here, I think we ended up with duplicate lambdas, stacks where named the same and something was crossing over. blowing away everything and redeploying seems to be running. Sorry about that:/ gesh
Open in Slack
PreviousNext
Powered by