Open wyattwalter opened 4 years ago
@wyattwalter @ricetj Does this need product support assistance or can we take the label off?
Hi @andreahewitt-odd.
Yes, I was hoping product support could help out with getting this across the finish line. JP said that he would take this on, but I forgot to add him as an assignee here.
User Story or Problem Statement
For VFS teams getting started with a new backend or using a new API within an existing backend, a common issue is that backends have little or inaccurate documentation about data expected and returned from the API. This makes doing things like building VCR cassettes and mocking test data very difficult. A few folks have come up with some creative solutions, but we believe that we can do better by providing a pattern that could be followed. How might we allow developers to interact with these backends through the VSP fwdproxy in lower environments directly from their development machines?
Goal
Enable and build patterns for developers to configure local installations of vets-api on their workstations to interact with lower environment backends through VSP's fwdproxy implementation.
Objectives or Key Results this is meant to further
Acceptance Criteria
How to configure this issue
product support
,analytics-insights
,operations
,triage
,tools-improvements
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,call center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)