We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
Firstly, I found your article at Medium very precise and useful. Thanks a lot sharing with us!!!
Reading the docs on the repository I found an information that is not completely true.
On README, you said:
Or use --aws-profile profileName when invoking sls CLI. Unfortunately there's no way to test it before you try to deploy.
But if we use SSM (EC2 Parameter Store) instead of an "env.yml" file, it's possible to test and get all necessary configuration directly from AWS.
And the tests can be done with command sls package --aws-profile <profile_name>.
sls package --aws-profile <profile_name>
Best regards!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
Firstly, I found your article at Medium very precise and useful. Thanks a lot sharing with us!!!
Reading the docs on the repository I found an information that is not completely true.
On README, you said:
But if we use SSM (EC2 Parameter Store) instead of an "env.yml" file, it's possible to test and get all necessary configuration directly from AWS.
And the tests can be done with command
sls package --aws-profile <profile_name>
.Best regards!
The text was updated successfully, but these errors were encountered: