For API calls to eFolder and an S3 cache miss, eFolder would go back to VBMS and get document then store to S3 before returning to Reader. This store to S3 is unnecessary because an ActiveJob is kicked off in Reader when user browses the list of document and caches all the documents. Our update behind a feature flag will return the document and not try to save to S3 for API calls. The ActiveJob will take the existing path and store to S3.
Resolves: APPEALS-46702
Description
For API calls to eFolder and an S3 cache miss, eFolder would go back to VBMS and get document then store to S3 before returning to Reader. This store to S3 is unnecessary because an ActiveJob is kicked off in Reader when user browses the list of document and caches all the documents. Our update behind a feature flag will return the document and not try to save to S3 for API calls. The ActiveJob will take the existing path and store to S3.
Acceptance Criteria Code compiles correctly Testing Plan https://jira.devops.va.gov/browse/APPEALS-49752 https://jira.devops.va.gov/browse/APPEALS-49753
User Facing Changes
[ ] Screenshots of UI changes added to PR & Original Issue
Code Documentation Updates
Database Changes
Only for Schema Changes
migrate:rollback
works as desired (change
supported functions)make docs
(after runningmake migrate
)Integrations: Adding endpoints for external APIs