-
Notifications
You must be signed in to change notification settings - Fork 4
[DTOSS-11293] - Create Production Environment & Enhance RBAC #586
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
[DTOSS-11293] - Create Production Environment & Enhance RBAC #586
Conversation
63365dc to
10ea648
Compare
c0f3331 to
0db733e
Compare
9bb560d to
27918a6
Compare
| variable "seed_demo_data" { | ||
| description = "Whether or not to seed the demo data in the database." | ||
| type = bool | ||
| default = false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought we were not going to put defaults on child modules to make them more transferable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead we put the defaults in
infrastructure/terraform/variables.tf
Take heed that all the other variables in this file ([infrastructure/modules/container-apps/variables.tf] do
not have defaults.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @mrlockstar , I've got a request from @saliceti to apply default values and remove from variables these values when appropriated, and I judged this to be one.
Happy to change if we all think it should be in the infrastructure/terraform/variables.tf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes we agreed to centralise default values at root module level
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed as agreed.
005bf70 to
9b38485
Compare
| storage_queues = ["notifications-message-status-updates", "notifications-message-batch-retries"] | ||
|
|
||
| always_allowed_paths = ["/sha"] | ||
| NO_OP_DATE = "0 0 31 2 *" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this used?
… RBAC - Add production Terraform variables configuration - Enable secure Key Vault integration for secret management - Configure production DNS (manage-breast-screening.nhs.uk) - Enable geo-redundant PostgreSQL backups for data protection - Set up production API endpoints and Front Door profile - Disable demo data seeding for production environment - Enable alerting and monitoring for production workloads - Enhance resource group init with RBAC for Entra ID groups - Implement group-based permission model in Bicep templates - Enable use_apex_domain to the environment Breaking changes: None (new production environment) Security: Key Vault protection and RBAC groups enabled Add false positive rbac role GUID entries to .gitleaksignore rename variables and remove from variables.yml and variables.tfvars variables with default values the same as values set including '/healthcheck' as always_allowed_paths on Front Door removing default value with module and let in root removing unused variable NO_OP_DATE
a41c547 to
8064b5c
Compare
Description
This PR introduces the production environment configuration for the NHS Digital breast screening management service, implementing secure infrastructure patterns and enhanced RBAC permissions for Entra ID groups using Azure Bicep templates.
Jira link
Changes Made
Production Environment Configuration
Enhanced Infrastructure Security
Security & Compliance Features
Following Azure best practices:
Infrastructure Highlights