You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this case is urgent, please subscribe to Subnet so that our 24/7 support team may help you faster.
Expected Behavior
The usage message of the subcommand mc ilm rule remove should mention mandatory parameter[s].
Current Behavior
mc ilm rule rm -h doesn't mention that the parameter --id must be provided and that it's mandatory. The website documents it though.
Possible Solution
Enhance the usage message.
Steps to Reproduce (for bugs)
mc ilm rule rm -h
Context
I tried to remove an ilm rule, and according to the current usage text I tried:
mc ilm rule rm s3-b71d733f-5d5a-4496-b083-2b15d9a91c4a/backup-b71d733f
mc: <ERROR> ilm ID cannot be empty. Invalid arguments provided, please refer `mc <command> -h` for relevant documentation.
but then it was unclear how to actually specify the id.
Regression
n/a
Your Environment
Version used (minio --version):
Server setup and configuration:
Operating System and version (uname -a): mc version RELEASE.2024-03-30T15-29-52Z (commit-id=9f8147bf0e037730077a1b3baef25e53181099b0)
The text was updated successfully, but these errors were encountered:
NOTE
If this case is urgent, please subscribe to Subnet so that our 24/7 support team may help you faster.
Expected Behavior
The usage message of the subcommand
mc ilm rule remove
should mention mandatory parameter[s].Current Behavior
mc ilm rule rm -h
doesn't mention that the parameter--id
must be provided and that it's mandatory. The website documents it though.Possible Solution
Enhance the usage message.
Steps to Reproduce (for bugs)
mc ilm rule rm -h
Context
I tried to remove an ilm rule, and according to the current usage text I tried:
but then it was unclear how to actually specify the id.
Regression
n/a
Your Environment
minio --version
):uname -a
):mc version RELEASE.2024-03-30T15-29-52Z (commit-id=9f8147bf0e037730077a1b3baef25e53181099b0)
The text was updated successfully, but these errors were encountered: