-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
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
Support --endpoint-url option #1194
Comments
this is currently coupled to s3, cloudformation and serverless repo endpoints. doesn't region already allow this? |
@honglu I understand why you want this, but I don't see how SAM CLI customers at large will want this. I am not inclined to supporting this as a CLI argument which adds cognitive load when a customer reads the help text to learn about the command. |
Having this would have been also cool and awesome to be able to test lambda function locally with LocalStack (local AWS environment), where we can create and mock dynamo tables and S3 in local stack and test ´sam local invoke --env-vars --endpoint-url=http://localstack-url´ that would target the LocalStack. this would save so many lives 😢 |
@bezdjian it would be nice indeed, and would remove the burden to use yet another library: https://github.com/localstack/aws-sam-cli-local |
Describe your idea/feature/enhancement
I wish SAM CLI would support
--endpoint-url
just like AWS CLI does.Here is the error I got when I tried to use
--endpoint-url
:Proposal
I think this option is probably not for every command under CLI but I think for the following command it makes sense:
The text was updated successfully, but these errors were encountered: