-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feat/opg scanning poc #6
Conversation
…dc php compoenents.
…rocessed jobs completed test with embedded callback.
… code and refactoring.
…tion, and slight refactor / clean-up of handler.go.
…support for both .env and yaml.
…d comments / clean-up.
- Configure CodeQL for Go - Add Dockerfile - Run tests in pipeline
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
…pression / refactor logger to use OPG.
…justice/opg-scanning into feat/opg-scanning-poc
… queue and update Dockerfile to ensure xsd docs are present.
Log in to ECR, then pull Trivy repositories from it. Use appropriate name for application ECR repository.
…justice/opg-scanning into feat/opg-scanning-poc
…ed job_queue_test.go to load multiple xml files directly.
…ntation and test coverage for lp1f validator
…dlers for multi page instances
… for specific fields.
…ADME.md removal, dateparser updated, and re-organisation
…/ logger updated.
…dle case stub creation.
d404faa
to
6645984
Compare
This service doesn't run its own terraform
So the tests can be run without needing environment variables to be set
I missed some bits
19e9864
to
151f688
Compare
Purpose
Initial POC setup in order to prepare the skeleton code for the migration from DDC PHP module to Go
Approach
Based on the continued analysis of DDC module we are encapsulating relative handlers for the workflow processing of documents. For the time being the code will represent a high-level outline of how the process is foreseen in Go and is subject to change.
Learning
Good dig of DDC module source code, and the setup of the docker environment (on-going)
Checklist