Unit test GH workflow

[pandu-k]

• Please check if the PR fulfills these requirements

• [ ] The commit message follows our guidelines

• [ ] Tests for the changes have been added (for bug fixes/features)

• [ ] Docs have been added / updated (for bug fixes / features)

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) new CI pipeline

• What is the current behavior? (You can also link to an open issue here) no unit test pipeline for py-marqo

• What is the new behavior (if this is a feature change)? a unit test pipeline for py-marqo

Test notes

• Tested and confirmed that this pipeline triggers after commits to a PR branch: https://github.com/marqo-ai/py-marqo/actions/runs/5733088797/ (failing because of a broken unit test)
• Does this pipeline trigger and work after a push to mainline: to be tested
• Does this pipeline work with manually specifying an ECR image: to be tested (must be merged into mainline before testing)
• Does this pipeline work with manually specifying an Docker image: to be tested (must be merged into mainline before testing)

Specifications:

• The test pipeline should run:
  • every time a PR is opened
  • every time code is merged into mainline
  • it can also be run manually
• Marqo should be pulled from an image repo and ran (to keep this pipeline fast)
• When manually running the pipeline, we indicate the Marqo image location, see attached image for a similar existing example
• To keep things simple, Marqo should run OpenSearch in a docker-in-docker configuration

Determining the Marqo version to use

The Marqo used for each py-marqo pipeline is:

• Default to the Dockerhub Marqo version specified in py-marqo.supported_marqo_version .
• Error out if it doesn’t exist

When we run manually we can specify a DockerHub or ECR image tag to run When testing

• build your feature branch into an ECR image to test against your py-marqo branch