-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create list of Platform Product-owned integrations to prevent silent failures #92926
Comments
See vets-api CODEOWNERS for files exclusively owned by backend-review-group. |
Assembled a list of endpoints and associated teams via CODEOWNERS. Cross-checking this data via Atlas and adding services as well. |
Finalizing report with data from Atlas, expecting to put have this available for review within the next day. |
Here is the spreadsheet with Platform endpoints and integrations -> https://docs.google.com/spreadsheets/d/1qqbkVT-lRpjxG58h3LKu3NczqJC2W7b7fYa93A6W_6A/edit?gid=1328380492#gid=1328380492 |
In review, received feedback that some of the endpoints designated as "Platform Owned" in Atlas are not. We only want "backend-review-group" only teams for this list of endpoints. Taking another pass on this list. |
Updated Platform endpoints -> https://docs.google.com/spreadsheets/d/1qqbkVT-lRpjxG58h3LKu3NczqJC2W7b7fYa93A6W_6A/edit?gid=1328380492#gid=1328380492 |
Published on Confluence -> https://vfs.atlassian.net/wiki/spaces/pilot/pages/3558572245/Platform+Owned+Endpoints+Integrations |
User Story
As the managers and developers of the VA Platform,
We need create a list of the list of integrations and endpoints that are managed within the VA system,
So that we know what integrations and endpoints will have to be watched for silent failures.
Issue Description
After the work for endpoints discovery is complete, we need to compile the list of integrations and endpoints that we need to monitor so that silent failures are eliminated.
Tasks
Success Metrics
The Platform Product team will be aware of the integrations and endpoints that are to be monitored to ensure against any silent failures.
Acceptance Criteria
Notes
Please review this guidance document for background and how-to discovery. This document was supplied by Matt Dingee.
Reference this document for past endpoint-specific work from the eMIS migration.
Validation
Assignee to add steps to this section. List the actions that need to be taken to confirm this issue is complete. Include any necessary links or context. State the expected outcome.
The text was updated successfully, but these errors were encountered: