Skip to content

[PRM-645] Updated get changed files to use bash for PR/Push condition#190

Merged
chrisbloe merged 3 commits intomainfrom
PRM-645-17
Jan 12, 2026
Merged

[PRM-645] Updated get changed files to use bash for PR/Push condition#190
chrisbloe merged 3 commits intomainfrom
PRM-645-17

Conversation

@oliverbeumkes-nhs
Copy link
Contributor

@oliverbeumkes-nhs oliverbeumkes-nhs commented Jan 12, 2026

No description provided.

@github-actions
Copy link

github-actions bot commented Jan 12, 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 hashicorp/aws versions matching ">= 5.20.0, >= 5.21.0, 5.37.0"...
- Finding latest version of hashicorp/archive...
- Installing hashicorp/aws v5.37.0...
- Installed hashicorp/aws v5.37.0 (signed by HashiCorp)
- Installing hashicorp/archive v2.7.1...
- Installed hashicorp/archive v2.7.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 (0 to add, 2 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-01-08T15:12:46.000+0000" -> (known after apply)
      ~ source_code_hash               = "MpLDFi2M+j9+z8J1conc1W5iey7NIeUd+yuRUS+Gv8c=" -> "HhOPwNtKI46Qg6mKXoxJivnR6gw9n7IlpTLGcK2Q+W0="
        tags                           = {
            "CreatedBy"   = "orphaned-record-continuity-infrastructure"
            "Environment" = "dev"
        }
        # (26 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

  # module.utils.aws_lambda_function.start-ecs-services-lambda[0] will be updated in-place
  ~ resource "aws_lambda_function" "start-ecs-services-lambda" {
        id                             = "ECSServiceStart"
        tags                           = {
            "CreatedBy"   = "orphaned-record-continuity-infrastructure"
            "Environment" = "dev"
        }
        # (28 unchanged attributes hidden)

      ~ environment {
          ~ variables = {
              ~ "DESIRED_COUNT_TEST" = "2" -> "1"
                # (1 unchanged element hidden)
            }
        }

        # (3 unchanged blocks hidden)
    }

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

@oliverbeumkes-nhs oliverbeumkes-nhs changed the title [PRM-645] Updated get chenged files to use bash for PR/Push condition [PRM-645] Updated get changed files to use bash for PR/Push condition Jan 12, 2026
@github-actions
Copy link

github-actions bot commented Jan 12, 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

github-actions bot commented Jan 12, 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

github-actions bot commented Jan 12, 2026

Report for mesh-forwarder

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 provider plugins...
- Finding hashicorp/aws versions matching "3.44.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.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 📖failure

Show Plan () 


Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_id" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_role" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.


Error: No value for required variable

  on variable.tf line 17:
  17: variable "task_image_tag" {

The root module input variable "task_image_tag" is not set, and has no
default value. Use a -var or -var-file command line argument to provide a
value for this variable.

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for re-registration-service

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 provider plugins...
- Finding hashicorp/aws versions matching "3.44.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.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 📖failure

Show Plan () 


Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_id" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_role" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.


Error: No value for required variable

  on variables.tf line 21:
  21: variable "task_image_tag" {

The root module input variable "task_image_tag" is not set, and has no
default value. Use a -var or -var-file command line argument to provide a
value for this variable.

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for ehr-transfer-service

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 provider plugins...
- Finding hashicorp/aws versions matching "3.44.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.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 📖failure

Show Plan () 


Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_id" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_role" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.


Error: No value for required variable

  on variables.tf line 18:
  18: variable "task_image_tag" {

The root module input variable "task_image_tag" is not set, and has no
default value. Use a -var or -var-file command line argument to provide a
value for this variable.

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for suspension-service

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...
- end-of-transfer-service in modules/end-of-transfer-service
- suspension-service in modules/suspension-service
Initializing provider plugins...
- Finding latest version of hashicorp/archive...
- Finding hashicorp/aws versions matching "5.59.0"...
- Installing hashicorp/archive v2.7.1...
- Installed hashicorp/archive v2.7.1 (signed by HashiCorp)
- Installing hashicorp/aws v5.59.0...
- Installed hashicorp/aws v5.59.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 📖failure

Show Plan () 


Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_id" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_role" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.


Error: No value for required variable

  on variables.tf line 16:
  16: variable "task_image_tag" {

The root module input variable "task_image_tag" is not set, and has no
default value. Use a -var or -var-file command line argument to provide a
value for this variable.

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for nems-event-processor

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 provider plugins...
- Finding hashicorp/aws versions matching "3.44.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.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 📖failure

Show Plan () 


Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_id" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_role" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.


Error: No value for required variable

  on variables.tf line 21:
  21: variable "task_image_tag" {

The root module input variable "task_image_tag" is not set, and has no
default value. Use a -var or -var-file command line argument to provide a
value for this variable.

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for pds-adaptor

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 provider plugins...
- Finding hashicorp/aws versions matching "4.48.0"...
- Installing hashicorp/aws v4.48.0...
- Installed hashicorp/aws v4.48.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 📖failure

Show Plan () 


Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_id" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_role" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.


Error: No value for required variable

  on variables.tf line 21:
  21: variable "task_image_tag" {

The root module input variable "task_image_tag" is not set, and has no
default value. Use a -var or -var-file command line argument to provide a
value for this variable.

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for gp2gp-messenger

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 provider plugins...
- Finding hashicorp/aws versions matching "~> 5.0"...
- Installing hashicorp/aws v5.100.0...
- Installed hashicorp/aws v5.100.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 📖failure

Show Plan () 


Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_id" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_role" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.


Error: No value for required variable

  on variables.tf line 15:
  15: variable "task_image_tag" {

The root module input variable "task_image_tag" is not set, and has no
default value. Use a -var or -var-file command line argument to provide a
value for this variable.

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for ehr-out-service

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 provider plugins...
- Finding hashicorp/aws versions matching "5.60.0"...
- Installing hashicorp/aws v5.60.0...
- Installed hashicorp/aws v5.60.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 📖failure

Show Plan () 


Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_id" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_role" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.


Error: No value for required variable

  on variables.tf line 17:
  17: variable "task_image_tag" {

The root module input variable "task_image_tag" is not set, and has no
default value. Use a -var or -var-file command line argument to provide a
value for this variable.

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for mhs

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 provider plugins...
- Finding hashicorp/aws versions matching "3.44.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.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, 3 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_cloudwatch_metric_alarm.inbound_nlb_down_errors will be updated in-place
  ~ resource "aws_cloudwatch_metric_alarm" "inbound_nlb_down_errors" {
      ~ dimensions                            = {
          ~ "LoadBalancer" = "app/dev-repo-mhs-out-alb/95f01e1ef1c15d88" -> "net/dev-repo-mhs-inbound/c5668e5303a26407"
          ~ "TargetGroup"  = "targetgroup/dev-repo-mhs-outbound/2965b97cc88ed832" -> "targetgroup/dev-repo-mhs-in-https/3e333c669edf7b00"
        }
        id                                    = "prm-mhs-infra service down"
      ~ namespace                             = "AWS/ApplicationELB" -> "AWS/NetworkELB"
        tags                                  = {}
        # (20 unchanged attributes hidden)
    }

  # aws_ecs_cluster.mhs_inbound_cluster will be updated in-place
  ~ resource "aws_ecs_cluster" "mhs_inbound_cluster" {
        id                 = "arn:aws:ecs:eu-west-2:[REDACTED_AWS_ACCOUNT_ID]:cluster/dev-repo-mhs-inbound-cluster"
        name               = "dev-repo-mhs-inbound-cluster"
        tags               = {
            "CreatedBy"   = "prm-mhs-infra"
            "Environment" = "dev"
            "Name"        = "dev-repo-mhs-cluster"
        }
        # (3 unchanged attributes hidden)

      + setting {
          + name  = "containerInsights"
          + value = "enabled"
        }
    }

  # aws_ecs_cluster.mhs_outbound_cluster will be updated in-place
  ~ resource "aws_ecs_cluster" "mhs_outbound_cluster" {
        id                 = "arn:aws:ecs:eu-west-2:[REDACTED_AWS_ACCOUNT_ID]:cluster/dev-repo-mhs-outbound-cluster"
        name               = "dev-repo-mhs-outbound-cluster"
        tags               = {
            "CreatedBy"   = "prm-mhs-infra"
            "Environment" = "dev"
            "Name"        = "dev-repo-mhs-outbound"
        }
        # (3 unchanged attributes hidden)

      + setting {
          + name  = "containerInsights"
          + value = "enabled"
        }
    }

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

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for ehr-repo

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 provider plugins...
- Finding hashicorp/aws versions matching "~> 4.0"...
- Installing hashicorp/aws v4.67.0...
- Installed hashicorp/aws v4.67.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 📖failure

Show Plan () 


Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_id" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Warning: Value for undeclared variable

The root module does not declare a variable named "common_account_role" but a
value was found in file "pipeline.auto.tfvars". If you meant to use this
value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.


Error: No value for required variable

  on variables.tf line 25:
  25: variable "task_image_tag" {

The root module input variable "task_image_tag" is not set, and has no
default value. Use a -var or -var-file command line argument to provide a
value for this variable.

@github-actions
Copy link

github-actions bot commented Jan 12, 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 hashicorp/aws versions matching ">= 5.20.0, >= 5.21.0, 5.37.0"...
- Finding latest version of hashicorp/archive...
- 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, 2 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-01-08T15:12:46.000+0000" -> (known after apply)
      ~ source_code_hash               = "MpLDFi2M+j9+z8J1conc1W5iey7NIeUd+yuRUS+Gv8c=" -> "5/3GDyXMhLdyHBrPPFj6nkTaVkaX8ag552XnSKZIEtw="
        tags                           = {
            "CreatedBy"   = "orphaned-record-continuity-infrastructure"
            "Environment" = "dev"
        }
        # (26 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

  # module.utils.aws_lambda_function.start-ecs-services-lambda[0] will be updated in-place
  ~ resource "aws_lambda_function" "start-ecs-services-lambda" {
        id                             = "ECSServiceStart"
        tags                           = {
            "CreatedBy"   = "orphaned-record-continuity-infrastructure"
            "Environment" = "dev"
        }
        # (28 unchanged attributes hidden)

      ~ environment {
          ~ variables = {
              ~ "DESIRED_COUNT_TEST" = "2" -> "1"
                # (1 unchanged element hidden)
            }
        }

        # (3 unchanged blocks hidden)
    }

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

@github-actions
Copy link

github-actions bot commented Jan 12, 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

github-actions bot commented Jan 12, 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

github-actions bot commented Jan 12, 2026

Report for mesh-forwarder

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 provider plugins...
- Finding hashicorp/aws versions matching "3.44.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.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_ecs_cluster.mesh-forwarder-ecs-cluster will be updated in-place
  ~ resource "aws_ecs_cluster" "mesh-forwarder-ecs-cluster" {
        id                 = "arn:aws:ecs:eu-west-2:[REDACTED_AWS_ACCOUNT_ID]:cluster/dev-mesh-forwarder-ecs-cluster"
        name               = "dev-mesh-forwarder-ecs-cluster"
        tags               = {
            "CreatedBy"   = "prm-deductions-mesh-forwarder"
            "Environment" = "dev"
            "Name"        = "dev-mesh-forwarder"
        }
        # (3 unchanged attributes hidden)

      + setting {
          + name  = "containerInsights"
          + value = "enabled"
        }
    }

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

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for re-registration-service

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 provider plugins...
- Finding hashicorp/aws versions matching "3.44.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.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_ecs_cluster.ecs-cluster will be updated in-place
  ~ resource "aws_ecs_cluster" "ecs-cluster" {
        id                 = "arn:aws:ecs:eu-west-2:[REDACTED_AWS_ACCOUNT_ID]:cluster/dev-re-registration-service-ecs-cluster"
        name               = "dev-re-registration-service-ecs-cluster"
        tags               = {
            "CreatedBy"   = "prm-repo-re-registration-service"
            "Environment" = "dev"
        }
        # (3 unchanged attributes hidden)

      + setting {
          + name  = "containerInsights"
          + value = "enabled"
        }
    }

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

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for suspension-service

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...
- end-of-transfer-service in modules/end-of-transfer-service
- suspension-service in modules/suspension-service
Initializing provider plugins...
- Finding latest version of hashicorp/archive...
- Finding hashicorp/aws versions matching "5.59.0"...
- Installing hashicorp/aws v5.59.0...
- Installed hashicorp/aws v5.59.0 (signed by HashiCorp)
- Installing hashicorp/archive v2.7.1...
- Installed hashicorp/archive v2.7.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

github-actions bot commented Jan 12, 2026

Report for ehr-out-service

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 provider plugins...
- Finding hashicorp/aws versions matching "5.60.0"...
- Installing hashicorp/aws v5.60.0...
- Installed hashicorp/aws v5.60.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 (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

github-actions bot commented Jan 12, 2026

Report for ehr-transfer-service

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 provider plugins...
- Finding hashicorp/aws versions matching "3.44.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.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 (1 to add, 2 to change, 1 to destroy) 


Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # aws_ecs_cluster.ehr_transfer_service_ecs_cluster will be updated in-place
  ~ resource "aws_ecs_cluster" "ehr_transfer_service_ecs_cluster" {
        id                 = "arn:aws:ecs:eu-west-2:[REDACTED_AWS_ACCOUNT_ID]:cluster/dev-ehr-transfer-service-ecs-cluster"
        name               = "dev-ehr-transfer-service-ecs-cluster"
        tags               = {
            "CreatedBy"   = "prm-repo-ehr-transfer-service"
            "Environment" = "dev"
            "Name"        = "dev-ehr-transfer-service"
        }
        # (3 unchanged attributes hidden)

      + setting {
          + name  = "containerInsights"
          + value = "enabled"
        }
    }

  # aws_ecs_service.ecs-service will be updated in-place
  ~ resource "aws_ecs_service" "ecs-service" {
        id                                 = "arn:aws:ecs:eu-west-2:[REDACTED_AWS_ACCOUNT_ID]:service/dev-ehr-transfer-service-ecs-cluster/dev-ehr-transfer-service"
        name                               = "dev-ehr-transfer-service"
        tags                               = {}
      ~ task_definition                    = "arn:aws:ecs:eu-west-2:[REDACTED_AWS_ACCOUNT_ID]:task-definition/ehr-transfer-service:749" -> (known after apply)
        # (14 unchanged attributes hidden)

        # (3 unchanged blocks hidden)
    }

  # aws_ecs_task_definition.task must be replaced
-/+ resource "aws_ecs_task_definition" "task" {
      ~ arn                      = "arn:aws:ecs:eu-west-2:[REDACTED_AWS_ACCOUNT_ID]:task-definition/ehr-transfer-service:749" -> (known after apply)
      ~ container_definitions    = (sensitive value) # forces replacement
      ~ id                       = "ehr-transfer-service" -> (known after apply)
      ~ revision                 = 749 -> (known after apply)
        tags                     = {
            "CreatedBy"   = "prm-repo-ehr-transfer-service"
            "Environment" = "dev"
        }
        # (10 unchanged attributes hidden)
    }

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

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for pds-adaptor

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 provider plugins...
- Finding hashicorp/aws versions matching "4.48.0"...
- Installing hashicorp/aws v4.48.0...
- Installed hashicorp/aws v4.48.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 (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

github-actions bot commented Jan 12, 2026

Report for gp2gp-messenger

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 provider plugins...
- Finding hashicorp/aws versions matching "~> 5.0"...
- Installing hashicorp/aws v5.100.0...
- Installed hashicorp/aws v5.100.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 (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

github-actions bot commented Jan 12, 2026

Report for nems-event-processor

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 provider plugins...
- Finding hashicorp/aws versions matching "3.44.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.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_ecs_cluster.ecs-cluster will be updated in-place
  ~ resource "aws_ecs_cluster" "ecs-cluster" {
        id                 = "arn:aws:ecs:eu-west-2:[REDACTED_AWS_ACCOUNT_ID]:cluster/dev-nems-event-processor-ecs-cluster"
        name               = "dev-nems-event-processor-ecs-cluster"
        tags               = {
            "CreatedBy"   = "prm-deductions-nems-event-processor"
            "Environment" = "dev"
        }
        # (3 unchanged attributes hidden)

      + setting {
          + name  = "containerInsights"
          + value = "enabled"
        }
    }

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

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for ehr-repo

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 provider plugins...
- Finding hashicorp/aws versions matching "~> 4.0"...
- Installing hashicorp/aws v4.67.0...
- Installed hashicorp/aws v4.67.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 (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

github-actions bot commented Jan 12, 2026

Report for mhs

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 provider plugins...
- Finding hashicorp/aws versions matching "3.44.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.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, 3 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_cloudwatch_metric_alarm.inbound_nlb_down_errors will be updated in-place
  ~ resource "aws_cloudwatch_metric_alarm" "inbound_nlb_down_errors" {
      ~ dimensions                            = {
          ~ "LoadBalancer" = "app/dev-repo-mhs-out-alb/95f01e1ef1c15d88" -> "net/dev-repo-mhs-inbound/c5668e5303a26407"
          ~ "TargetGroup"  = "targetgroup/dev-repo-mhs-outbound/2965b97cc88ed832" -> "targetgroup/dev-repo-mhs-in-https/3e333c669edf7b00"
        }
        id                                    = "prm-mhs-infra service down"
      ~ namespace                             = "AWS/ApplicationELB" -> "AWS/NetworkELB"
        tags                                  = {}
        # (20 unchanged attributes hidden)
    }

  # aws_ecs_cluster.mhs_inbound_cluster will be updated in-place
  ~ resource "aws_ecs_cluster" "mhs_inbound_cluster" {
        id                 = "arn:aws:ecs:eu-west-2:[REDACTED_AWS_ACCOUNT_ID]:cluster/dev-repo-mhs-inbound-cluster"
        name               = "dev-repo-mhs-inbound-cluster"
        tags               = {
            "CreatedBy"   = "prm-mhs-infra"
            "Environment" = "dev"
            "Name"        = "dev-repo-mhs-cluster"
        }
        # (3 unchanged attributes hidden)

      + setting {
          + name  = "containerInsights"
          + value = "enabled"
        }
    }

  # aws_ecs_cluster.mhs_outbound_cluster will be updated in-place
  ~ resource "aws_ecs_cluster" "mhs_outbound_cluster" {
        id                 = "arn:aws:ecs:eu-west-2:[REDACTED_AWS_ACCOUNT_ID]:cluster/dev-repo-mhs-outbound-cluster"
        name               = "dev-repo-mhs-outbound-cluster"
        tags               = {
            "CreatedBy"   = "prm-mhs-infra"
            "Environment" = "dev"
            "Name"        = "dev-repo-mhs-outbound"
        }
        # (3 unchanged attributes hidden)

      + setting {
          + name  = "containerInsights"
          + value = "enabled"
        }
    }

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

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Report for ehr-repo-db-roles

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 provider plugins...
- Finding hashicorp/aws versions matching "3.44.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.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 (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.

chrisbloe
chrisbloe approved these changes Jan 12, 2026
View reviewed changes
Copy link
Contributor

@chrisbloe chrisbloe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's try this getting the changes identified.

@chrisbloe chrisbloe merged commit e6064fd into main Jan 12, 2026
38 of 39 checks passed
@chrisbloe chrisbloe deleted the PRM-645-17 branch January 12, 2026 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@chrisbloe chrisbloe chrisbloe approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@oliverbeumkes-nhs @chrisbloe