Moto. Mokai AWS
Testing is an integral part of the development process. And sometimes developers are required to run tests locally, before committing changes.
If the application uses Amazon Web Services , the moto python library is ideal for this.
A complete list of resources can be found here .
On Github there is a turnip Hugo Picado - a moto-server . Ready image, run and use. The only nuance is that after launch, no AWS resources have been created there yet.
Well, it's easy enough to fix.
Since it is necessary to specify the type of service at startup (the env variable MOTO_SERVICE ), we need to describe the creation of the resource.
')
Change start.sh a bit:
Instead
Paste:
The resulting file is obtained:
Build a new image and push into your registry.
Next, we will write a resource initialization script, for example, SWF domain , using the library for working with AWS - boto3:
The logic is as follows:
And, you can mock the whole resource by running one container:
We try interactively:
Works!
Thus, we can do docker-compose.yml, which will help save time for testing changes:
Actually, not only on the developer's laptop you can use this approach. Preliminary tests with mocks after assembly will help to get rid of possible problems when running on dev * environments.
References:
Motocker repo - github.com/picadoh/motocker
Moto repo - github.com/spulec/moto
Boto3 Docs - boto3.amazonaws.com/v1/documentation/api/latest/index.html
If the application uses Amazon Web Services , the moto python library is ideal for this.
A complete list of resources can be found here .
On Github there is a turnip Hugo Picado - a moto-server . Ready image, run and use. The only nuance is that after launch, no AWS resources have been created there yet.
Well, it's easy enough to fix.
Since it is necessary to specify the type of service at startup (the env variable MOTO_SERVICE ), we need to describe the creation of the resource.
')
Change start.sh a bit:
Instead
moto_server $MOTO_SERVICE -H $MOTO_HOST -p $MOTO_PORT Paste:
if [ -f /opt/init/bootstrap.py ]; then moto_server $MOTO_SERVICE -H $MOTO_HOST -p $MOTO_PORT & (sleep 5 && echo "Executing bootstrap script." && python /opt/init/bootstrap.py) else moto_server $MOTO_SERVICE -H $MOTO_HOST -p $MOTO_PORT fi wait The resulting file is obtained:
start.sh
#!/bin/sh # validate required input if [ -z "$MOTO_SERVICE" ]; then echo "Please define AWS service to run with Moto Server (eg s3, ec2, etc)" exit 1 fi # setting defaults for optional input if [ -z "$MOTO_HOST" ]; then MOTO_HOST="0.0.0.0" fi if [ -z "$MOTO_PORT" ]; then MOTO_PORT="5000" fi echo "Starting service $MOTO_SERVICE at $MOTO_HOST:$MOTO_PORT" if [ -f /opt/init/bootstrap.py ]; then moto_server $MOTO_SERVICE -H $MOTO_HOST -p $MOTO_PORT & (sleep 5 && echo "Executing bootstrap script." && python /opt/init/bootstrap.py) else moto_server $MOTO_SERVICE -H $MOTO_HOST -p $MOTO_PORT fi # Prevent container from exiting when bootstrap.py finishing wait Build a new image and push into your registry.
Next, we will write a resource initialization script, for example, SWF domain , using the library for working with AWS - boto3:
bootstrap_swf.py
import boto3 from botocore.exceptions import ClientError import os os.environ["AWS_ACCESS_KEY_ID"] = "fake" os.environ["AWS_SECRET_ACCESS_KEY"] = "fake" client = boto3.client('swf', region_name='us-west-2', endpoint_url='http://localhost:5000') try: client.register_domain( name='test-swf-mock-domain', description="Test SWF domain", workflowExecutionRetentionPeriodInDays="10" ) except ClientError as e: print "Domain already exists: ", e.response.get("Error", {}).get("Code") response = client.list_domains( registrationStatus='REGISTERED', maximumPageSize=123, reverseOrder=True|False ) print 'Ready' The logic is as follows:
- Mount our script at startup in /opt/init/bootstrap.py .
- If the file is mounted, it will be executed.
- If the file does not exist, the bare moto-server will start.
And, you can mock the whole resource by running one container:
docker run --name swf -d \ -e MOTO_SERVICE=swf \ -e MOTO_HOST=0.0.0.0 \ -e MOTO_PORT=5000 \ -p 5001:5000 \ -v /tmp/bootstrap_swf.py:/opt/init/bootstrap.py \ -i awesome-repo.com/moto-server:latest We try interactively:
Works!
Thus, we can do docker-compose.yml, which will help save time for testing changes:
docker-compose.yml
version: '3' services: s3: image: picadoh/motocker environment: - MOTO_SERVICE=s3 - MOTO_HOST=10.0.1.2 ports: - "5002:5000" networks: motonet: ipv4_address: 10.0.1.2 volumes: - /tmp/bootstrap_s3.py:/opt/init/bootstrap.py swf: image: picadoh/motocker environment: - MOTO_SERVICE=swf - MOTO_HOST=10.0.1.3 ports: - "5001:5000" networks: motonet: ipv4_address: 10.0.1.3 volumes: - /tmp/bootstrap_swf.py:/opt/init/bootstrap.py ec2: image: picadoh/motocker environment: - MOTO_SERVICE=ec2 - MOTO_HOST=10.0.1.4 ports: - "5003:5000" networks: motonet: ipv4_address: 10.0.1.4 volumes: - /tmp/bootstrap_ec2.py:/opt/init/bootstrap.py networks: motonet: driver: bridge ipam: config: - subnet: 10.0.0.0/16 Actually, not only on the developer's laptop you can use this approach. Preliminary tests with mocks after assembly will help to get rid of possible problems when running on dev * environments.
References:
Motocker repo - github.com/picadoh/motocker
Moto repo - github.com/spulec/moto
Boto3 Docs - boto3.amazonaws.com/v1/documentation/api/latest/index.html
Source: https://habr.com/ru/post/454334/
All Articles