Skip to content
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

Closed
4 tasks
juddin927 opened this issue Sep 25, 2023 · 9 comments
Closed
4 tasks

Create VPC module #456

juddin927 opened this issue Sep 25, 2023 · 9 comments
Assignees
Labels
enhancement New feature or request

Comments

@juddin927
Copy link
Contributor

juddin927 commented Sep 25, 2023

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

  • Documentation has been written / updated
  • README has been updated
  • Another team member has reviewed
  • Tests are green
@juddin927 juddin927 added the enhancement New feature or request label Sep 25, 2023
@tomwells98
Copy link
Contributor

To discuss at after stand up

@tomwells98
Copy link
Contributor

Ticket to be updated with the list of 10 repos in scope and the two out of scope

@tomwells98
Copy link
Contributor

To be refined further by devs

@tomwells98 tomwells98 added enhancement New feature or request and removed enhancement New feature or request labels Dec 7, 2023
@smjmoj
Copy link

smjmoj commented Dec 11, 2023

We have the following repos with multiple VPC management with the following versions.

`
PaloAlto-pipelines == source = "github.com/ministryofjustice/terraform-aws-vpc?ref=v0.1.5"

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
`

@smjmoj
Copy link

smjmoj commented Dec 11, 2023

Decision is to update each VPC to use the latest starting with the oldest
staff-device-logging-infrastructure == 2.50.0

then
network-access-control-infrastructure == 2.78.0

then
staff-device-dns-dhcp-infrastructure pinned locally to 3.14.0

then
nvvs-devops-monitor == 5.1.1
staff-device-shared-services-infrastructure == 5.1.1
staff-infrastructure-network-services == 5.1.1

Current version is 5.4

Then in order to reduce noise configure Dependabot to inform us when the version 6x is released or CVEs

@tomwells98
Copy link
Contributor

A new path forward to be defined on the next engineers meeting on 18/12/2023.

@juddin927
Copy link
Contributor Author

@juddin927
Copy link
Contributor Author

@juddin927
Copy link
Contributor Author

@juddin927 juddin927 self-assigned this Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants