COS Bucket Module Missing Support for Multiple Expiry Rules

[vnyagarwal]

Description

We need support for configuring multiple expiry rules for a COS bucket. The latest Terraform module does not support this capability.

Current module (v10.2.12):
https://registry.terraform.io/modules/terraform-ibm-modules/cos/ibm/10.2.12

Limitation: Expiry rule is supported only as a string, not as a list.

Requirement: Ability to define multiple rules as a list, so that multiple expiry policies can be applied to the same bucket.

Note: COS UI already supports multiple expiry rules.

Impact: Inability to manage multiple expiry rules through IaC, requiring manual setup via UI, which is non-compliant with automation standards.

By submitting this issue, you agree to follow our Code of Conduct

[shemau]

The current implementation uses the ibm_cos_bucket_lifecycle_configuration resource

  dynamic "lifecycle_rule" {
    ## This for_each block is NOT a loop to attach to multiple expiration blocks.
    ## This block is only used to conditionally add expiration block depending on expire rule is enabled.
    for_each = local.expire_enabled
    content {
      expiration {
        days = var.expire_days
      }
      filter {
        prefix = var.expire_filter_prefix != null ? var.expire_filter_prefix : ""
      }
      rule_id = "expiry-rule"
      status  = "enable"
    }
  }

Which enables 0 or 1 rules to be created and is opinionated about the rule_id.

There are two variables associated with this feature:

• expire_days: defaults to 365 in the main module
• expire_filter_prefix: defaults to null in the main module

The default behavior is therefor to create a lifecycle expiry rule at 365 days.

The feature is also enabled via the buckets module.

There are two variables associated with the feature:

• expire_rule: defaults to enable: false, days: 365
• expire_filter_prefix: defaults to null

If the enable flag is true, only then is the days value passed into the main module.

The default behavior is there to not create a lifecycle expiry rule.

Given the radically different default behaviors, it would be difficult to retain existing behavior AND to implement a feature that optional create 0 or more lifecycle expiry rules.

It would be possible to add a new module lifecycle_rules that took a bucket and a map of expiry rules (plus potentially other types of rules). This module would allow full flexibility for complex scenarios, whilst the main module/buckets module retains backward compatibility with a single rule. It would require the consumer to iterate over any buckets that required complex rules and it would not be available via as deployable architecture.

[vnyagarwal]

@Aayush-Abhyarthi, Could you please provide an update on when we can expect this issue to be fixed and the feature to be available?

[Aayush-Abhyarthi]

Update:- This feature will not be a part of Q3 commitment.