This microservice generates teams from a fixed file of names.
It uses AWS.
Notice that this service is not accumulative. It always generates all the teams.
- So, if you execute this service to generate 5 teams
and then you execute this service again,
you will end up with 5 teams, instead of 10. - That is, only the last execution of this service counts.
Create a package of this service to upload to the lambda on AWS this way:
-
Execute this script from the lambda folder:
./scripts/package_with_dockerfile.sh
-
Upload the zip file generated in the 'build' directory to the AWS Lambda:
lambda.zip
Create a package of this service to upload to the lambda on AWS this way:
-
Execute this script from the lambda folder:
./scripts/package.sh
-
Upload the zip file generated in the 'build' directory to the AWS Lambda:
lambda.zip
This change is necessary because of limitations of Git Bash for Windows
when resolving paths.,
Edit this file and replace PATH_TO_THIS_LAMBDA_ON_WINDOWS with the lambda path:
./scripts/other/package-win-alt.sh
Create a package of this service to upload to the lambda on AWS this way:
-
Execute this script from the lambda folder:
./scripts/other/package-win-alt.sh
-
Upload the zip file generated in the 'build' directory to the AWS Lambda:
lambda.zip
You can use package options 2 and 3 to execute the unit tests inside the container.
If the tests pass, the package will be created;
otherwise, the package will not be created.
We assume that the tests are written using pytest.
To execute the unit tests, execute the script with the argument: --devtest