Anders Wasen

We have the "common/not so secret" parameters in `serverless-secrets` and want to have "more secret" things (e.g. private keys, passwords, API keys) in KMS. The main reason for not using...

Second this, or at least be able to use OS vars, e.g. `export ENVIRONMENT=qa`

``` export const lookupPEPPOLCd = async (countryCd, searchScheme) => { try { const query = await PEPPOLCountryList.query(countryCd) .filter('schemeID') .contains(searchScheme) .execAsync() .then(reply => reply.Items.map(item => item.get())); return query[0].peppolCd; } catch (err)...

Ugh... Shoul'da done some loggin first... Did some more testing and found that the variables that exists in AWS SSM (i.e. "online") is used if they exist, so e.g., `/dev/lambda/common/PG_USER`...

Some more info... sorry about long thread... I changed to using `local` stage and it all runs fine, but as before I get the Serverless warning. So I added the...

The "problem" is that Servless itself overwrites the variables from AWS SSM. I added a `console.log()` to both packages and it logs like: ``` serverless-offline-ssm reading variables Serverless: serverless-offline-ssm checking...

https://github.com/serverless/serverless/issues/9460#issuecomment-839918367

It already exists support in https://github.com/didikeke/gm-base64/. Maybe something to work from?

Any updates on this? We are using a bunch of micro-services and the Lambda Function URL, while great as a function has put some hurdles for us developing and testing......

> > could create > > `localhost:3003` `localhost:3004` > > and/or > > `localhost:3003/foo` `localhost:3003/bar` I'd prefer the second approach and run it on the same port as Serverless Offline....