Yasuke/moto
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

AWSLambda: Improve docs (#7374)

Browse Source
This commit is contained in:
Bert Blommers 2024-02-20 23:06:46 +00:00 committed by GitHub
parent 56d11d841c
commit f7b8a92212
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/docs/configuration/index.rst
View File

@ -49,6 +49,9 @@ That is why Moto resets the `boto3-Session`, to make sure that it is recreated w
If all of your tests use Moto, and you never want to reach out to AWS, you can choose to _not_ reset the `boto3-session`. New boto3-clients that are created will reuse the `boto3-Session` (with fake credentials), making Moto much more performant. If all of your tests use Moto, and you never want to reach out to AWS, you can choose to _not_ reset the `boto3-session`. New boto3-clients that are created will reuse the `boto3-Session` (with fake credentials), making Moto much more performant.
Other configuration options
---------------------------
.. toctree:: .. toctree::
:maxdepth: 1 :maxdepth: 1

8
moto/awslambda/models.py
View File

@ -1815,7 +1815,9 @@ class LambdaBackend(BaseBackend):
Implementation of the AWS Lambda endpoint. Implementation of the AWS Lambda endpoint.
Invoking functions is supported - they will run inside a Docker container, emulating the real AWS behaviour as closely as possible. Invoking functions is supported - they will run inside a Docker container, emulating the real AWS behaviour as closely as possible.
It is possible to connect from AWS Lambdas to other services, as long as you are running MotoProxy or the MotoServer. .. warning:: When invoking a function using the decorators, the created Docker container cannot reach Moto (or it's in-memory state). Any AWS SDK-requests within your Lambda will try to connect to AWS instead.
It is possible to connect from AWS Lambdas to other services, as long as you are running MotoProxy or the MotoServer in a Docker container.
When running the MotoProxy, calls to other AWS services are automatically proxied. When running the MotoProxy, calls to other AWS services are automatically proxied.
@ -1876,15 +1878,13 @@ class LambdaBackend(BaseBackend):
MOTO_LAMBDA_DATA_DIR=/tmp/data MOTO_LAMBDA_DATA_DIR=/tmp/data
.. note:: When using the decorators, a Docker container cannot reach Moto, as the Docker-container loses all mock-context. Any boto3-invocations used within your Lambda will try to connect to AWS.
_-_-_-_ _-_-_-_
If you want to mock the Lambda-containers invocation without starting a Docker-container, use the simple decorator: If you want to mock the Lambda-containers invocation without starting a Docker-container, use the simple decorator:
.. sourcecode:: python .. sourcecode:: python
@mock_lambda_simple @mock_aws(config={"lambda": {"use_docker": False}})
""" """