department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
281 stars 197 forks source link

Discovery: Run Postman Collection against EKS-Next Cluster #87368

Closed pjhill closed 1 month ago

pjhill commented 1 month ago

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

Acceptance Criteria

pjhill commented 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

pjhill commented 1 month ago

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.

pjhill commented 1 month ago

Scheduled a meeting with Patrick and Ben for tomorrow afternoon. I'm hoping to work out a plan of attack for the implementation.

pjhill commented 1 month ago

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.

pjhill commented 1 month ago

Design document is available here -- https://vfs.atlassian.net/wiki/spaces/PRT/pages/3292790785/GitHub+Actions+Test+Framework+Execution+Design+Document