...
Please fill out the centralized wiki page: Frankfurt Release Platform Maturity
- Document current upgrade component strategy
- For the application itself, since it's based on microservices, it's easy to replace the docker containers with the required version. The main focus for upgrade is to adapt the application to the database related changes. To achieve, we intend to add new DDLs as script files with a specific version number into the new docker image, assuring that each new image has all DDLs (which reflect the changes on the database) contained in older images. We use the version number of the script files as a trace to upgrade our application by running the script files contained in the image version by version.
- SECCOM Perform Software Composition Analysis - Vulnerability tables
- We'll check and update the vulnerability table of Holmes before each milestone comes. The corresponding ticket could be found in JIRA backlog.
- SECCOM Password removal from OOM HELM charts
- There's no password in OOM HELM chart for HOLMES.
- SECCOM HTTPS communication vs. HTTP
- There's a switch for users within Holmes to decide whether they want to enable HTTP or not. By default, HTTP is disabled for Holmes containers. But users could enable it by changing the parameter when running the docker container.
API Incoming Dependencies
...
Please update any risk on the centralized wiki page - Frankfurt Risks
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...