Closed pjhill closed 1 month ago
Analysis is available in this Confluence document -- https://vfs.atlassian.net/wiki/spaces/PRT/pages/3279913340/Postman+Collection+Execution+Against+vets-api+in+EKS-Next+Cluster
Currently experimenting with running the vets-api
postman collection from inside the postman/newman docker hub image and hitting a local instance of vets-api
running in Docker. For some reason, the postman/newman docker container can't hit the vets-api
instance using localhost
.
Scheduled a meeting with Patrick and Ben for tomorrow afternoon. I'm hoping to work out a plan of attack for the implementation.
Next step from the meeting is to create and refine a design document. I will work on and review that design document with Ben and Patrick. Once the design document is finalized we will share that with the Product team and create additional tickets for implementation of the design document.
Design document is available here -- https://vfs.atlassian.net/wiki/spaces/PRT/pages/3292790785/GitHub+Actions+Test+Framework+Execution+Design+Document
Description
Given that we want to be able to run our Postman test collection against any
vets-api
instance running in any EKS cluster, we need to come up with a solution that does not rely on external routing being setup. Consider solutions that allow the Postman collection to be retrieved into any EKS cluster, executed against an internal (to the cluster)vets-api
instance, and reported out of the cluster for on-demand review.Consider
vets-api
is confirmed to be up and runningAcceptance Criteria