-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fix docker image check for faster OCR deployments #354
Conversation
path: ./frontend/client.tgz | ||
api-endpoint: https://reportvision-ocr-${{ inputs.deploy-env }}.azurewebsites.net/ | ||
frontend-tarball: ./frontend.tgz | ||
frontend-path: ./frontend |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
def doing a lot of scope creeping on this PR but its a needed clean-up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great move to clean up the environments, to be consistent with the terraform code.
name: production-files | ||
path: ./frontend/client.tgz | ||
api-endpoint: https://reportvision-ocr-${{ inputs.deploy-env }}.azurewebsites.net/ | ||
frontend-tarball: ./frontend.tgz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the npm packages being installed in the ./frontend.tgz
file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thats correct. at least with GHA, packaging all the frontend files into a tarball/zip makes downloading from other jobs smoother.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
We temporarily disabled the docker image checker cause it was bugging out, just to get the deployment automation moving forward. Now we have the time to fix it.
Screenshots (if applicable)
Related Issues
[Link any related issues or tasks from your project management system.]
Checklist