website
website copied to clipboard
Does Not Support Profiles
The .env file is non-standard and requires scripting to switch out or tokenize the .env for different AWS environments. Please update to support 'profile' in yml that references ~/.aws/credentials entries
Thanks for your feedback @kling-appfire ... that sounds reasonable. The issue is that if we are trying to support all providers, and profile in n~/.aws/credentials is AWS specific. So we figured the best middle ground here is to rely on .env files since everyone is familiar with env vars.
Thanks. Are there plans to make website/component a 1st Class Enterprise service? So we could have provider/profile and inline ${opt.variable} and ${self.variable}? Put me on the updates list for that! :)
@kling-appfire @eahefnawy I am using the aws profile via npm script like this "deploy:sls": "serverless --aws-profile <yourprofile name>". I do not use .env file for this and works fine.
@kling-appfire @eahefnawy I am using the aws profile via npm script like this
"deploy:sls": "serverless --aws-profile <yourprofile name>". I do not use .env file for this and works fine.
Thank you! I'll try that.