-
Notifications
You must be signed in to change notification settings - Fork 290
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
Move RAM association job to reusable workflow and switch secrets source to AWS Secrets Manager #8993
base: main
Are you sure you want to change the base?
Conversation
Terraform Plan Summarysingle-sign-on |
Terraform Plan Summarymodernisation-platform-account |
Terraform Plan Summarycore-vpc-preproduction |
Terraform Plan Summarycore-vpc-development |
Terraform Plan Summarycore-vpc-test |
Terraform Plan Summarycore-vpc-production |
Terraform Plan Summarypagerduty |
|
Terraform Plan Summarycore-security-production |
Terraform Plan Summarycore-logging-production |
Terraform Plan Summarycore-shared-services-production |
Terraform Plan Summarygithub |
Terraform Plan Summarycore-network-services-production |
Terraform Plan Summarygithub |
Terraform Plan Summarysingle-sign-on |
Terraform Plan Summarymodernisation-platform-account |
Terraform Plan Summarycore-vpc-production |
Terraform Plan Summarycore-vpc-development |
Terraform Plan Summarycore-vpc-preproduction |
Terraform Plan Summarycore-vpc-test |
Terraform Plan Summarypagerduty |
|
Terraform Plan Summarycore-security-production |
Terraform Plan Summarycore-logging-production |
Terraform Plan Summarycore-shared-services-production |
Terraform Plan Summarygithub |
Terraform Plan Summarysingle-sign-on |
Terraform Plan Summarypagerduty |
Terraform Plan Summarymodernisation-platform-account |
Terraform Plan Summarygithub |
Terraform Plan Summarycore-network-services-production |
A reference to the issue / Description of it
This PR refactors the current workflow by moving the
member-account-ram-association
job to a reusable workflow. In addition, it updates the source from which secrets are fetched: instead of using GitHub Secrets, we now fetch the secrets directly from AWS Secrets Manager. This change improves security and scalability by keeping sensitive secrets centralized in AWS. #8233 #7109How does this PR fix the problem?
Centralized Secrets Management: Previously, In workflows, secrets were fetched from GitHub Secrets. Now, secrets are fetched from AWS Secrets Manager, ensuring better security practices and centralization of secrets management.
Reusable Workflow: By moving the
member-account-ram-association
job to a reusable workflow, we enable better reuse and maintainability of the job across different workflows. The job now only runs when required, controlled by therun_ram_association
input.How has this been tested?
Please describe the tests that you ran and provide instructions to reproduce.
{Please write here}
Deployment Plan / Instructions
Will this deployment impact the platform and / or services on it?
{Please write here}
Checklist (check
x
in[ ]
of list items)Additional comments (if any)
{Please write here}