-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lifecycle option not present in latest docker images #3498
Comments
Yes, it is available only via mc client/API |
See #3470. |
Thank you! Maybe a small update in the docs might help others to not look for this feature anymore. |
@feorlen ^^^ |
@GabrielDumbrava @ramondeklein We updated the docs when several features were removed, let me see if there's some dangling reference or other confusing bit we could improve. Thanks for mentioning! |
feorlen
added a commit
to minio/docs
that referenced
this issue
Jan 28, 2025
Add a clearer callout to `mc` for features not/no longer available in MinIO Console. Given that several things were removed, enumerating specific commands seems impractical? Opinions solicited. From a community issue: minio/console#3498 Not yet staged. --------- Co-authored-by: Ravind Kumar <ravind@min.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
If you add a bucket with versioning enabled you should have the option to add lifecycle rules.
Current Behavior
For the docker images newer than and including
RELEASE.2024-12-13T22-19-12Z
if you create a bucket with versioning enabled you are not presented with the option to create lifecycle rules.Steps to Reproduce (for bugs)
Create a bucket, enable versioning for it. The
Lifecycle
option is not presented.Context
Not able to create lifecycle rules from the Management Console.
Regression
The latest version/image where the option is presented is
RELEASE.2024-11-07T00-52-20Z
, which is a few months old already.Your Environment
I'm using the docker images on Linux.
The text was updated successfully, but these errors were encountered: