Skip to content

Conversation

@Monkatron95
Copy link
Contributor

No description provided.

@Monkatron95 Monkatron95 self-assigned this Nov 11, 2025
@Monkatron95 Monkatron95 requested a review from a team as a code owner November 11, 2025 16:23
@sys-terraform-applier
Copy link

sys-terraform-applier bot commented Nov 11, 2025

Terraform run output for

Cluster: dev-aws
Module: pubsub/kafka-shared-msk-backup-bucket-retention
Path: dev-aws/kafka-shared-msk/msk-backup-bucket-retention
Commit ID: 2e6f24d99e4f0c01025fa6f8c8947772c3dd8e3c
✅ Run Status: Ok, Run Summary: 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_s3_bucket_lifecycle_configuration.msk_topics_retention will be updated in-place
  ~ resource "aws_s3_bucket_lifecycle_configuration" "msk_topics_retention" {
        id                                     = "uw-dev-pubsub-msk-backup"
        # (4 unchanged attributes hidden)

      ~ rule {
            id     = "unicom.status-bill-email-connector"
            # (2 unchanged attributes hidden)

          ~ expiration {
              ~ days                         = 92 -> 8
                # (1 unchanged attribute hidden)
            }

            # (1 unchanged block hidden)
        }
      ~ rule {
            id     = "unicom.status-energy-smets1-notifier"
            # (2 unchanged attributes hidden)

          ~ expiration {
              ~ days                         = 92 -> 8
                # (1 unchanged attribute hidden)
            }

            # (1 unchanged block hidden)
        }
      ~ rule {
            id     = "unicom.status-finance-email-delivery-engine"
            # (2 unchanged attributes hidden)

          ~ expiration {
              ~ days                         = 92 -> 8
                # (1 unchanged attribute hidden)
            }

            # (1 unchanged block hidden)
        }
      ~ rule {
            id     = "unicom.status-v2"
            # (2 unchanged attributes hidden)

          ~ expiration {
              ~ days                         = 92 -> 8
                # (1 unchanged attribute hidden)
            }

            # (1 unchanged block hidden)
        }
      ~ rule {
            id     = "unicom.status"
            # (2 unchanged attributes hidden)

          ~ expiration {
              ~ days                         = 92 -> 8
                # (1 unchanged attribute hidden)
            }

            # (1 unchanged block hidden)
        }

        # (184 unchanged blocks hidden)
    }

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

To manually trigger plan again please post @terraform-applier plan dev-aws/kafka-shared-msk/msk-backup-bucket-retention as comment.

@sys-terraform-applier
Copy link

sys-terraform-applier bot commented Nov 11, 2025

Terraform run output for

Cluster: dev-aws
Module: pubsub/kafka-shared-msk-unicom
Path: dev-aws/kafka-shared-msk/unicom
Commit ID: 8846a6ec13aba8b0f9fe9ee4dd1c3bc43a113fb5
✅ Run Status: Ok, Run Summary: Plan: 0 to add, 5 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:

  # kafka_topic.unicom_status will be updated in-place
  ~ resource "kafka_topic" "unicom_status" {
      ~ config             = {
          ~ "retention.ms"          = "7889400000" -> "604800000"
            # (5 unchanged elements hidden)
        }
        id                 = "unicom.status"
        name               = "unicom.status"
        # (2 unchanged attributes hidden)
    }

  # kafka_topic.unicom_status_bill_email_connector will be updated in-place
  ~ resource "kafka_topic" "unicom_status_bill_email_connector" {
      ~ config             = {
          ~ "retention.ms"          = "7889400000" -> "604800000"
            # (5 unchanged elements hidden)
        }
        id                 = "unicom.status-bill-email-connector"
        name               = "unicom.status-bill-email-connector"
        # (2 unchanged attributes hidden)
    }

  # kafka_topic.unicom_status_energy_smets1_notifier will be updated in-place
  ~ resource "kafka_topic" "unicom_status_energy_smets1_notifier" {
      ~ config             = {
          ~ "retention.ms"          = "7889400000" -> "604800000"
            # (5 unchanged elements hidden)
        }
        id                 = "unicom.status-energy-smets1-notifier"
        name               = "unicom.status-energy-smets1-notifier"
        # (2 unchanged attributes hidden)
    }

  # kafka_topic.unicom_status_finance_email_delivery_engine will be updated in-place
  ~ resource "kafka_topic" "unicom_status_finance_email_delivery_engine" {
      ~ config             = {
          ~ "retention.ms"          = "7889400000" -> "604800000"
            # (5 unchanged elements hidden)
        }
        id                 = "unicom.status-finance-email-delivery-engine"
        name               = "unicom.status-finance-email-delivery-engine"
        # (2 unchanged attributes hidden)
    }

  # kafka_topic.unicom_status_v2 will be updated in-place
  ~ resource "kafka_topic" "unicom_status_v2" {
      ~ config             = {
          ~ "retention.ms"          = "7889400000" -> "604800000"
            # (5 unchanged elements hidden)
        }
        id                 = "unicom.status-v2"
        name               = "unicom.status-v2"
        # (2 unchanged attributes hidden)
    }

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

To manually trigger plan again please post @terraform-applier plan dev-aws/kafka-shared-msk/unicom as comment.

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.

3 participants