Skip to content

[PRM-691] Introduction of strict tagging when releasing#202

Merged
oliverbeumkes-nhs merged 46 commits intomainfrom
PRM-691
Mar 17, 2026
Merged

[PRM-691] Introduction of strict tagging when releasing#202
oliverbeumkes-nhs merged 46 commits intomainfrom
PRM-691

Conversation

@oliverbeumkes-nhs
Copy link
Copy Markdown
Contributor

No description provided.

@oliverbeumkes-nhs oliverbeumkes-nhs marked this pull request as ready for review February 24, 2026 16:03
@oliverbeumkes-nhs oliverbeumkes-nhs requested a review from a team as a code owner February 24, 2026 16:03
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 6, 2026

Report for deductions

Terraform Initialization ⚙️success

Initialization Output

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing modules...
- deductions-core in modules/deductions-core
Downloading registry.terraform.io/terraform-aws-modules/vpc/aws 5.5.2 for deductions-core.vpc...
- deductions-core.vpc in .terraform/modules/deductions-core.vpc
- deductions-private in modules/deductions-private
- deductions-private.mq-admin in modules/deductions-private/mq-admin
Downloading registry.terraform.io/terraform-aws-modules/vpc/aws 5.5.2 for deductions-private.vpc...
- deductions-private.vpc in .terraform/modules/deductions-private.vpc
Downloading registry.terraform.io/terraform-aws-modules/dynamodb-table/aws 4.0.0 for ehr_transfer_tracker_dynamodb_table...
- ehr_transfer_tracker_dynamodb_table in .terraform/modules/ehr_transfer_tracker_dynamodb_table
- repo in modules/mhs
- repo.cluster in modules/mhs/cluster-network
- test-harness in modules/mhs
- test-harness.cluster in modules/mhs/cluster-network
- utils in modules/utils
Initializing provider plugins...
- Finding latest version of hashicorp/archive...
- Finding hashicorp/aws versions matching ">= 5.20.0, >= 5.21.0, 5.37.0"...
- Installing hashicorp/archive v2.7.1...
- Installed hashicorp/archive v2.7.1 (signed by HashiCorp)
- Installing hashicorp/aws v5.37.0...
- Installed hashicorp/aws v5.37.0 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Terraform Validation 🤖success

Validation Output

Success! The configuration is valid.


Terraform Plan 📖success

Show Plan (0 to add, 1 to change, 0 to destroy)


Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # aws_lambda_function.generate_cost_report_lambda will be updated in-place
  ~ resource "aws_lambda_function" "generate_cost_report_lambda" {
        id                             = "dev-generate-cost-report-lambda"
      ~ last_modified                  = "2026-03-04T11:26:50.000+0000" -> (known after apply)
      ~ source_code_hash               = "3dVLoBm2bx1Ta2E2sOVlM5F9sM/om26m3tpjuVHcfsc=" -> "PZPUzRCdOSYEMGhYL0i7o0bfzS5Ty92vcNxz91ObGG4="
        tags                           = {
            "CreatedBy"   = "orphaned-record-continuity-infrastructure"
            "Environment" = "dev"
        }
        # (26 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 6, 2026

Report for deductions-dashboard

Terraform Initialization ⚙️success

Initialization Output

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing modules...
- error_count_widgets in widgets/error_count_widget
- health_lb_widgets in widgets/health_lb_widget
- health_widgets in widgets/health_widget
- queue_metrics_widgets in widgets/queue_metrics_widget
- repo_error_count_widgets in widgets/error_count_widget
- repo_health_lb_widgets in widgets/health_lb_widget
- repo_health_network_lb_widgets in widgets/health_network_lb_widget
- repo_health_widgets in widgets/health_widget
- repo_mq_metrics_widgets in widgets/mq_metrics_widget
- repo_queue_metrics_widgets in widgets/queue_metrics_widget
- repo_task_widgets in widgets/task_widget
- task_widgets in widgets/task_widget
Initializing provider plugins...
- Finding hashicorp/aws versions matching "~> 3.0"...
- Installing hashicorp/aws v3.76.1...
- Installed hashicorp/aws v3.76.1 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Terraform Validation 🤖success

Validation Output

Success! The configuration is valid.


Terraform Plan 📖success

Show Plan (no changes)


No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 6, 2026

Report for deductions-cross-account

Terraform Initialization ⚙️success

Initialization Output

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing modules...
- ci_roles in iam-ci
- environment_roles in iam-environment
- environment_strict_roles in iam-strict-environment
Initializing provider plugins...
- Finding hashicorp/aws versions matching "~> 3.0"...
- Installing hashicorp/aws v3.76.1...
- Installed hashicorp/aws v3.76.1 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Terraform Validation 🤖success

Validation Output

Success! The configuration is valid.


Terraform Plan 📖success

Show Plan (no changes)


No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

@github-actions
Copy link
Copy Markdown

Checkov issues found

View full details here.

@github-actions
Copy link
Copy Markdown

Checkov issues found

View full details here.

@github-actions
Copy link
Copy Markdown

Checkov issues found

View full details here.

@github-actions
Copy link
Copy Markdown

Checkov issues found

View full details here.

@github-actions
Copy link
Copy Markdown

Checkov issues found

View full details here.

samfallowfield
samfallowfield previously approved these changes Mar 16, 2026
@github-actions
Copy link
Copy Markdown

Checkov issues found

View full details here.

@github-actions
Copy link
Copy Markdown

Checkov issues found

View full details here.

@github-actions
Copy link
Copy Markdown

Checkov issues found

View full details here.

@github-actions
Copy link
Copy Markdown

Checkov issues found

View full details here.

@github-actions
Copy link
Copy Markdown

Checkov issues found

View full details here.

@sonarqubecloud
Copy link
Copy Markdown

@oliverbeumkes-nhs oliverbeumkes-nhs merged commit fd141c4 into main Mar 17, 2026
25 of 26 checks passed
@oliverbeumkes-nhs oliverbeumkes-nhs deleted the PRM-691 branch March 17, 2026 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants