changes in core-shared-service plans

[markgov]

User Story

As a modernisation platform engineer
I expect terraform plans for the core-shared-service account not to produce any changes
So that we can have clean runs

Value / Purpose

Currently when a plan is run even on main it is changing the following items everytime

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

Terraform will perform the following actions:

  # aws_vpc_endpoint_route_table_association.live-data-additional will be created
  + resource "aws_vpc_endpoint_route_table_association" "live-data-additional" {
      + id              = (known after apply)
      + route_table_id  = "rtb-0cdcff9a04595eae3"
      + vpc_endpoint_id = "vpce-0de6559d7259c0071"
    }

  # module.instance_scheduler.aws_lambda_function.this will be updated in-place
  ~ resource "aws_lambda_function" "this" {
        id                             = "instance-scheduler-lambda-function"
      ~ image_uri                      = (sensitive value)
      ~ last_modified                  = "2024-12-20T09:19:31.000+0000" -> (known after apply)
        tags                           = {}
        # (26 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

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

Context / Background

This is unexpected and seems to be happening everytime a plan is run on the account

Useful Contacts

No response

Additional Information

No response

Definition of Done

• Find out why this is happening
• implement a code fix
• issue reviewed

[dms1981]

Resolved via #8842