-
Notifications
You must be signed in to change notification settings - Fork 1
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 VPC module #456
Comments
To discuss at after stand up |
Ticket to be updated with the list of 10 repos in scope and the two out of scope |
To be refined further by devs |
We have the following repos with multiple VPC management with the following versions. ` network-access-control-infrastructure == 2.78.0 nvvs-devops-monitor == 5.1.1 staff-device-dns-dhcp-infrastructure pinned locally to 3.14.0 staff-device-logging-infrastructure == 2.50.0 staff-device-shared-services-infrastructure == 5.1.1 staff-infrastructure-network-services == 5.1.1 |
Decision is to update each VPC to use the latest starting with the oldest then then then Current version is 5.4 Then in order to reduce noise configure Dependabot to inform us when the version 6x is released or CVEs |
A new path forward to be defined on the next engineers meeting on 18/12/2023. |
ministryofjustice/network-access-control-infrastructure#258 for dependabot |
User Story
We aim to separate the VPC module in our codebase from the community module and transition it into a self-hosted module.
Value / Purpose
The community module undergoes frequent changes, adding unnecessary complexity with limited benefits. Every time a new version is released, Dependabot detects the changes and refactoring often requires substantial effort. Transitioning to a self-hosted module will enable us to eliminate unnecessary dependencies and streamline the process.
Useful Contacts
No response
Additional Information
No response
Definition of Done
The text was updated successfully, but these errors were encountered: