Skip to content

Conversation

@Aditya-ranjan-16
Copy link
Contributor

@Aditya-ranjan-16 Aditya-ranjan-16 commented Nov 11, 2025

Description

Added a new lifecycle_rules submodule which allows to add multiple expiry lifecycle rules to an existing cos bucket
https://github.ibm.com/GoldenEye/issues/issues/15834

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

This PR Adds a new lifecycle_rules submodule which allows to add multiple expiry lifecycle rules to an existing cos bucket

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@Aditya-ranjan-16 Aditya-ranjan-16 marked this pull request as ready for review November 20, 2025 18:59
@Aditya-ranjan-16
Copy link
Contributor Author

/run pipeline

2 similar comments
@Aditya-ranjan-16
Copy link
Contributor Author

/run pipeline

@Aditya-ranjan-16
Copy link
Contributor Author

/run pipeline

Comment on lines +21 to +25
variable "object_versioning_enabled" {
description = "Whether to enable object versioning to keep multiple versions of an object in a bucket."
type = bool
default = false
}
Copy link
Contributor

Choose a reason for hiding this comment

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

This does not do this. In fact this is not used in the code anywhere. It is only used in cross variable validation.

This is not a pattern used anywhere in the TIM, AFAIK.

output, err := options.RunTestConsistency()
assert.Nil(t, err, "This should not have errored")
assert.NotNil(t, output, "Expected some output")
}
Copy link
Contributor

Choose a reason for hiding this comment

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

PR tests cannot be overlooked for a whole module.

I think sufficient coverage would be to update the basic example to use the new module, the same way it validates the buckets module.

Extending the basic example would mean no need for any additional example code, or additional tests.

Copy link
Member

Choose a reason for hiding this comment

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

Why are we not adding archive rule as well?

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.

4 participants