Updates to mc docs for December 2022 releases (#697)

This PR applies updates to numerous files to address changes in the two
December 2022 `mc` releases.

- Deprecates `mc admin bucket quota` and links to new commands
- Adds `mc quota set | clear | info` commands
- Adds `attach | detach` subcommands to `mc admin idp ldap policy`
- Updates list of call types available to `mc admin trace`
- Updates `mc` page with new commands
- Fixes minor errors in `mc cp`
- Adds `--limit-*` flags to global flag options
- Adds `--versions` flag to `mc find`
    
Closes #685

- Updates ilm commands for new structure for tiers and rules
    
    - Deprecates `mc admin tier`
- Deprecates `mc ilm add | edit | export | import | ls | rm` commands
    - Adds new `mc ilm rule` and six subcommands
    - Adds new `mc ilm tier` and six subcommands
    - Updates references to ilm and admin tier  commands throughout docs
    - Adds new deprecated commands page
    - Adds `mc ilm rule` and `mc ilm tier` holding pages with toctrees

- Closes #691
- Closes #662

source/administration/identity-access-management/policy-based-access-control.rst

@@ -769,12 +769,12 @@ services:
 .. policy-action:: admin:SetTier
 
    Allows creating and modifying remote storage tiers using the 
-   :mc:`mc admin tier` command.
+   :mc:`mc ilm tier` commands.
 
 .. policy-action:: admin:ListTier
 
    Allows listing configured remote storage tiers using the
-   :mc:`mc admin tier` command.
+   :mc:`mc ilm tier` commands.
 
 .. policy-action:: admin:BandwidthMonitor
 

source/administration/object-management/create-lifecycle-management-expiration-rule.rst

@@ -62,51 +62,51 @@ transition lifecycle management rules on any bucket in the cluster:.
 Expire Objects after Number of Days
 -----------------------------------
 
-Use :mc:`mc ilm add` with :mc-cmd:`~mc ilm add --expire-days` to
+Use :mc:`mc ilm rule add` with :mc-cmd:`~mc ilm rule add --expire-days` to
 expire bucket contents a number of days after object creation:
 
 .. code-block:: shell
    :class: copyable
 
-   mc ilm add ALIAS/PATH --expire-days "DAYS" 
+   mc ilm rule add ALIAS/PATH --expire-days "DAYS" 
 
-- Replace :mc-cmd:`ALIAS <mc ilm add ALIAS>` with the 
+- Replace :mc-cmd:`ALIAS <mc ilm rule add ALIAS>` with the 
   :mc:`alias <mc alias>` of the S3-compatible host.
 
-- Replace :mc-cmd:`PATH <mc ilm add ALIAS>` with the path to the bucket on the
+- Replace :mc-cmd:`PATH <mc ilm rule add ALIAS>` with the path to the bucket on the
   S3-compatible host.
 
-- Replace :mc-cmd:`DAYS <mc ilm add --expire-days>` with the number of days after
+- Replace :mc-cmd:`DAYS <mc ilm rule add --expire-days>` with the number of days after
   which to expire the object. For example, specify ``30`` to expire the
   object 30 days after creation.
 
 Expire Versioned Objects
 ------------------------
 
-Use :mc:`mc ilm add` to expiring noncurrent object versions and object
+Use :mc:`mc ilm rule add` to expiring noncurrent object versions and object
 delete markers: 
 
 - To expire noncurrent object versions after a specific duration in days,
-  include :mc-cmd:`~mc ilm add --noncurrent-expire-days`.
+  include :mc-cmd:`~mc ilm rule add --noncurrent-expire-days`.
 
 - To expire delete markers for objects with no remaining versions, 
-  include :mc-cmd:`~mc ilm add --expire-delete-marker`.
+  include :mc-cmd:`~mc ilm rule add --expire-delete-marker`.
 
 .. code-block:: shell
    :class: copyable
 
-   mc ilm add ALIAS/PATH \ 
+   mc ilm rule add ALIAS/PATH \ 
       --noncurrent-expire-days NONCURRENT_DAYS \
       --expire-delete-marker
 
-- Replace :mc-cmd:`ALIAS <mc ilm add ALIAS>` with the 
+- Replace :mc-cmd:`ALIAS <mc ilm rule add ALIAS>` with the 
   :mc:`alias <mc alias>` of the S3-compatible host.
 
-- Replace :mc-cmd:`PATH <mc ilm add ALIAS>` with the path to the bucket on the
+- Replace :mc-cmd:`PATH <mc ilm rule add ALIAS>` with the path to the bucket on the
   S3-compatible host.
 
 - Replace :mc-cmd:`NONCURRENT_DAYS 
-  <mc ilm add --noncurrent-expire-days>` with the number of days after
+  <mc ilm rule add --noncurrent-expire-days>` with the number of days after
   which to expire noncurrent object versions. For example, specify ``30d`` to
   expire a version after it has been noncurrent for at least 30 days.
 

source/administration/object-management/object-lifecycle-management.rst

@@ -35,8 +35,8 @@ MinIO supports any of the following remote tier targets:
 MinIO object transition supports use cases like moving aged data from MinIO clusters in private or public cloud infrastructure to low-cost private or public cloud storage solutions. 
 MinIO manages retrieving tiered objects on-the-fly without any additional application-side logic. 
 
-Use the :mc:`mc admin tier` command to create a remote target for tiering data that target. 
-You can then use the :mc-cmd:`mc ilm add --transition-days` command to transition objects to that tier after a specified number of calendar days.
+Use the :mc:`mc ilm tier add` command to create a remote target for tiering data to that target. 
+You can then use the :mc-cmd:`mc ilm rule add --transition-days` command to transition objects to that tier after a specified number of calendar days.
 
 .. versionadded:: RELEASE.2022-11-10T18-20-21Z
 
@@ -72,7 +72,7 @@ Versioned Buckets
 MinIO adopts :s3-docs:`S3 behavior <intro-lifecycle-rules.html#intro-lifecycle-rules-actions>` for transition rules on :ref:`versioned buckets <minio-bucket-versioning>`. 
 Specifically, MinIO by default applies the transition operation to the *current* object version. 
 
-To transition noncurrent object versions, specify the :mc-cmd:`~mc ilm add --noncurrent-transition-days` and :mc-cmd:`~mc ilm add --noncurrent-transition-tier` options when creating the transition rule. 
+To transition noncurrent object versions, specify the :mc-cmd:`~mc ilm rule add --noncurrent-transition-days` and :mc-cmd:`~mc ilm rule add --noncurrent-transition-tier` options when creating the transition rule. 
 
 .. _minio-lifecycle-management-expiration:
 
@@ -85,7 +85,7 @@ For example, you can create a lifecycle management rule to expire any object old
 
 .. todo: Diagram of MinIO Expiration
 
-Use :mc-cmd:`mc ilm add --expire-days` to expire objects after a specified number of calendar days.
+Use :mc-cmd:`mc ilm rule add --expire-days` to expire objects after a specified number of calendar days.
 
 For buckets with :ref:`replication <minio-bucket-replication>` configured, MinIO does not replicate objects deleted by a lifecycle management expiration rule.
 See :ref:`minio-replication-behavior-delete` for more information.
@@ -98,11 +98,11 @@ MinIO has two specific default behaviors for versioned buckets:
 
 - MinIO applies the expiration option to only the *current* object version by creating a ``DeleteMarker`` as is normal with versioned delete.
 
-  To expire noncurrent object versions, specify the :mc-cmd:`~mc ilm add --noncurrent-expire-days` option when creating the expiration rule. 
+  To expire noncurrent object versions, specify the :mc-cmd:`~mc ilm rule add --noncurrent-expire-days` option when creating the expiration rule. 
 
 - MinIO does not expire ``DeleteMarkers`` *even if* no other versions of that object exist.
 
-  To expire delete markers when there are no remaining versions for that object, specify the :mc-cmd:`~mc ilm add --expire-delete-marker` option when creating the expiration rule.
+  To expire delete markers when there are no remaining versions for that object, specify the :mc-cmd:`~mc ilm rule add --expire-delete-marker` option when creating the expiration rule.
 
 .. _minio-lifecycle-management-scanner:
 

source/administration/object-management/transition-objects-to-azure.rst

@@ -117,18 +117,16 @@ Procedure
 2) Configure the Remote Storage Tier
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc admin tier add` command to add a new remote storage tier:
+Use the :mc-cmd:`mc ilm tier add` command to add a new remote storage tier:
 
 .. code-block:: shell
    :class: copyable
 
-   mc admin tier add azure TARGET TIER_NAME \
-      --endpoint https://HOSTNAME
-      --bucket BUCKET \
-      --prefix PREFIX
+   mc ilm tier add azure TARGET TIER_NAME \
       --account-name ACCOUNT \
       --account-key KEY \
-      --region REGION
+      --bucket BUCKET \
+      --prefix PREFIX
 
 
 The example above uses the following arguments:
@@ -141,24 +139,20 @@ The example above uses the following arguments:
    * - Argument
      - Description
    
-   * - :mc-cmd:`TARGET <mc admin tier add TARGET>`
+   * - :mc-cmd:`TARGET <mc ilm tier add TARGET>`
      - The :mc:`alias <mc alias>` of the MinIO deployment on which to configure
        the remote tier.
    
-   * - :mc-cmd:`TIER_NAME <mc admin tier add TIER_NAME>`
+   * - :mc-cmd:`TIER_NAME <mc ilm tier add TIER_NAME>`
      - The name to associate with the new :abbr:`Azure (Microsoft Azure)` blob
        remote storage tier. Specify the name in all-caps, e.g. ``AZURE_TIER``.
        This value is required in the next step.
 
-   * - :mc-cmd:`HOSTNAME <mc admin tier add --endpoint>`
-     - The URL endpoint for the :abbr:`Azure (Microsoft Azure)` storage
-       backend.
-
-   * - :mc-cmd:`BUCKET <mc admin tier add --bucket>`
+   * - :mc-cmd:`BUCKET <mc ilm tier add --bucket>`
      - The name of the bucket on the :abbr:`Azure (Microsoft Azure)` storage
        backend to which MinIO transitions objects.
 
-   * - :mc-cmd:`PREFIX <mc admin tier add --prefix>`
+   * - :mc-cmd:`PREFIX <mc ilm tier add --prefix>`
      - The optional bucket prefix within which MinIO transitions objects.
 
        MinIO stores all transitioned objects in the specified ``BUCKET`` under a
@@ -171,7 +165,7 @@ The example above uses the following arguments:
        source MinIO deployment to faciliate ease of operations related to
        diagnostics, maintenance, or disaster recovery.
 
-   * - :mc-cmd:`ACCOUNT <mc admin tier add --account-name>`
+   * - :mc-cmd:`ACCOUNT <mc ilm tier add --account-name>`
      - The account name MinIO uses to access the bucket. The account name
        *must* correspond to an :abbr:`Azure (Microsoft Azure)` user with the
        required :ref:`permissions
@@ -179,13 +173,9 @@ The example above uses the following arguments:
 
        You cannot change this account name after creating the tier.
 
-   * - :mc-cmd:`KEY <mc admin tier add --account-key>`
+   * - :mc-cmd:`KEY <mc ilm tier add --account-key>`
      - The corresponding key for the specified ``ACCOUNT``.
 
-   * - :mc-cmd:`REGION <mc admin tier add --region>`
-     - The :abbr:`Azure (Microsoft Azure)` blob storage region of the specified
-       ``BUCKET``. You can safely omit this option if the ``HOSTNAME`` includes
-       the region.
 
 3) Create and Apply the Transition Rule
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -198,16 +188,15 @@ The example above uses the following arguments:
 4) Verify the Transition Rule
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc:`mc ilm ls` command to review the configured transition
-rules:
+Use the :mc:`mc ilm rule ls` command to review the configured transition rules:
 
 .. code-block:: shell
    :class: copyable
 
-   mc ilm ls ALIAS/PATH --transition
+   mc ilm rule ls ALIAS/PATH --transition
 
-- Replace :mc-cmd:`ALIAS <mc ilm ls ALIAS>` with the :mc:`alias <mc alias>`
+- Replace :mc-cmd:`ALIAS <mc ilm rule ls ALIAS>` with the :mc:`alias <mc alias>`
   of the MinIO deployment.
 
-- Replace :mc-cmd:`PATH <mc ilm ls ALIAS>` with the name of the bucket for
+- Replace :mc-cmd:`PATH <mc ilm rule ls ALIAS>` with the name of the bucket for
   which to retrieve the configured lifecycle management rules.

source/administration/object-management/transition-objects-to-gcs.rst

@@ -115,18 +115,16 @@ Procedure
 2) Configure the Remote Storage Tier
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc admin tier add` command to add a new Google Cloud Storage
+Use the :mc-cmd:`mc ilm tier add` command to add a new Google Cloud Storage
 service as the remote storage tier:
 
 .. code-block:: shell
    :class: copyable
 
-   mc admin tier add gcs TARGET TIER_NAME \
-      --endpoint https://HOSTNAME \
+   mc ilm tier add gcs TARGET TIER_NAME \
       --bucket BUCKET \
       --prefix PREFIX \
-      --credentials-file CREDENTIALS \
-      --region REGION
+      --credentials-file CREDENTIALS
 
 The example above uses the following arguments:
 
@@ -138,24 +136,28 @@ The example above uses the following arguments:
    * - Argument
      - Description
 
-   * - :mc-cmd:`TARGET <mc admin tier add TARGET>`
+   * - :mc-cmd:`TARGET <mc ilm tier add TARGET>`
      - The :mc:`alias <mc alias>` of the MinIO deployment on which to configure
        the :abbr:`GCS (Google Cloud Storage)` remote tier.
    
-   * - :mc-cmd:`TIER_NAME <mc admin tier add TIER_NAME>`
+   * - :mc-cmd:`TIER_NAME <mc ilm tier add TIER_NAME>`
      - The name to associate with the new :abbr:`GCS (Google Cloud Storage)` 
        remote storage tier. Specify the name in all-caps, e.g. ``GCS_TIER``.
        This value is required in the next step.
 
-   * - :mc-cmd:`HOSTNAME <mc admin tier add --endpoint>`
-     - The URL endpoint for the :abbr:`GCS (Google Cloud Storage)` storage
-       backend.
+   * - :mc-cmd:`CREDENTIALS <mc ilm tier add --credentials-file>`
+     - The `credential file
+       <https://cloud.google.com/docs/authentication/getting-started>`__ for a
+       user on the remote GCS tier. The specified user credentials *must*
+       correspond to a GCS user with the required
+       :ref:`permissions 
+       <minio-lifecycle-management-transition-to-gcs-permissions-remote>`.
 
-   * - :mc-cmd:`BUCKET <mc admin tier add --bucket>`
+   * - :mc-cmd:`BUCKET <mc ilm tier add --bucket>`
      - The name of the bucket on the :abbr:`GCS (Google Cloud Storage)` storage
        backend to which MinIO transitions objects.
 
-   * - :mc-cmd:`PREFIX <mc admin tier add --prefix>`
+   * - :mc-cmd:`PREFIX <mc ilm tier add --prefix>`
      - The optional bucket prefix within which MinIO transitions objects.
 
        MinIO stores all transitioned objects in the specified ``BUCKET`` under a
@@ -168,18 +170,6 @@ The example above uses the following arguments:
        source MinIO deployment to faciliate ease of operations related to
        diagnostics, maintenance, or disaster recovery.
 
-   * - :mc-cmd:`CREDENTIALS <mc admin tier add --credentials-file>`
-     - The `credential file
-       <https://cloud.google.com/docs/authentication/getting-started>`__ for a
-       user on the remote GCS tier. The specified user credentials *must*
-       correspond to a GCS user with the required
-       :ref:`permissions 
-       <minio-lifecycle-management-transition-to-gcs-permissions-remote>`.
-
-   * - :mc-cmd:`REGION <mc admin tier add --region>`
-     - The :abbr:`GCS (Google Cloud Storage)` region of the specified
-       ``BUCKET``. You can safely omit this
-       option if the ``HOSTNAME`` includes the region.
 
 3) Create and Apply the Transition Rule
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -192,16 +182,16 @@ The example above uses the following arguments:
 4) Verify the Transition Rule
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc:`mc ilm ls` command to review the configured transition
+Use the :mc:`mc ilm rule ls` command to review the configured transition
 rules:
 
 .. code-block:: shell
    :class: copyable
 
-   mc ilm ls ALIAS/PATH --transition
+   mc ilm rule ls ALIAS/PATH --transition
 
-- Replace :mc-cmd:`ALIAS <mc ilm ls ALIAS>` with the :mc:`alias <mc alias>`
+- Replace :mc-cmd:`ALIAS <mc ilm rule ls ALIAS>` with the :mc:`alias <mc alias>`
   of the MinIO deployment.
 
-- Replace :mc-cmd:`PATH <mc ilm ls ALIAS>` with the name of the bucket for
+- Replace :mc-cmd:`PATH <mc ilm rule ls ALIAS>` with the name of the bucket for
   which to retrieve the configured lifecycle management rules.

source/administration/object-management/transition-objects-to-s3.rst

@@ -124,20 +124,20 @@ Procedure
 2) Configure the Remote Storage Tier
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc admin tier add` command to add an Amazon S3 service as the
+Use the :mc-cmd:`mc ilm tier add` command to add an Amazon S3 service as the
 new remote storage tier:
 
 .. code-block:: shell
    :class: copyable
 
-   mc admin tier add s3 TARGET TIER_NAME \
-      --endpoint https://HOSTNAME \
-      --bucket BUCKET \
-      --prefix PREFIX
-      --access-key ACCESS_KEY \
-      --secret-key SECRET_KEY \
-      --region REGION \
-      --storage-class STORAGE_CLASS
+   mc ilm tier add s3 TARGET TIER_NAME  \
+      --endpoint https://HOSTNAME       \
+      --access-key ACCESS_KEY           \
+      --secret-key SECRET_KEY           \
+      --bucket BUCKET                   \
+      --prefix PREFIX                   \
+      --storage-class STORAGE_CLASS     \
+      --region REGION 
 
 The example above uses the following arguments:
 
@@ -149,23 +149,33 @@ The example above uses the following arguments:
    * - Argument
      - Description
    
-   * - :mc-cmd:`TARGET <mc admin tier add TARGET>`
+   * - :mc-cmd:`TARGET <mc ilm tier add TARGET>`
      - The :mc:`alias <mc alias>` of the MinIO deployment on which to configure
        the S3 remote tier.
    
-   * - :mc-cmd:`TIER_NAME <mc admin tier add TIER_NAME>`
+   * - :mc-cmd:`TIER_NAME <mc ilm tier add TIER_NAME>`
      - The name to associate with the new S3 remote storage tier. Specify the
        name in all-caps, e.g. ``S3_TIER``. This value is required in the next
        step.
 
-   * - :mc-cmd:`HOSTNAME <mc admin tier add --endpoint>`
+   * - :mc-cmd:`HOSTNAME <mc ilm tier add --endpoint>`
      - The URL endpoint for the S3 storage backend.
 
-   * - :mc-cmd:`BUCKET <mc admin tier add --bucket>`
+   * - :mc-cmd:`ACCESS_KEY <mc ilm tier add --access-key>`
+     - The S3 access key MinIO uses to access the bucket. The
+       access key *must* correspond to an IAM user with the 
+       required 
+       :ref:`permissions 
+       <minio-lifecycle-management-transition-to-s3-permissions-remote>`.
+
+   * - :mc-cmd:`SECRET_KEY <mc ilm tier add --secret-key>`
+     - The corresponding secret key for the specified ``ACCESS_KEY``.
+
+   * - :mc-cmd:`BUCKET <mc ilm tier add --bucket>`
      - The name of the bucket on the S3 storage backend to which MinIO
        transitions objects.
 
-   * - :mc-cmd:`PREFIX <mc admin tier add --prefix>`
+   * - :mc-cmd:`PREFIX <mc ilm tier add --prefix>`
      - The optional bucket prefix within which MinIO transitions objects.
 
        MinIO stores all transitioned objects in the specified ``BUCKET`` under a
@@ -178,27 +188,17 @@ The example above uses the following arguments:
        source MinIO deployment to faciliate ease of operations related to
        diagnostics, maintenance, or disaster recovery.
 
-   * - :mc-cmd:`ACCESS_KEY <mc admin tier add --access-key>`
-     - The S3 access key MinIO uses to access the bucket. The
-       access key *must* correspond to an IAM user with the 
-       required 
-       :ref:`permissions 
-       <minio-lifecycle-management-transition-to-s3-permissions-remote>`.
-
-   * - :mc-cmd:`SECRET_KEY <mc admin tier add --secret-key>`
-     - The corresponding secret key for the specified ``ACCESS_KEY``.
-
-   * - :mc-cmd:`REGION <mc admin tier add --region>`
-     - The AWS S3 region of the specified ``BUCKET``. You can safely omit this
-       option if the ``HOSTNAME`` includes the region.
-
-   * - :mc-cmd:`STORAGE_CLASS <mc admin tier add --storage-class>`
+   * - :mc-cmd:`STORAGE_CLASS <mc ilm tier add --storage-class>`
      - The S3 storage class to which MinIO transitions objects. Specify
        one of the following supported storage classes:
 
        - ``STANDARD``
        - ``REDUCED``
 
+   * - :mc-cmd:`REGION <mc ilm tier add --region>`
+     - The AWS S3 region of the specified ``BUCKET``. You can safely omit this
+       option if the ``HOSTNAME`` includes the region.
+
 3) Create and Apply the Transition Rule
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -210,16 +210,16 @@ The example above uses the following arguments:
 4) Verify the Transition Rule
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc:`mc ilm ls` command to review the configured transition
+Use the :mc:`mc ilm rule ls` command to review the configured transition
 rules:
 
 .. code-block:: shell
    :class: copyable
 
-   mc ilm ls ALIAS/PATH --transition
+   mc ilm rule ls ALIAS/PATH --transition
 
-- Replace :mc-cmd:`ALIAS <mc ilm ls ALIAS>` with the :mc:`alias <mc alias>`
+- Replace :mc-cmd:`ALIAS <mc ilm rule ls ALIAS>` with the :mc:`alias <mc alias>`
   of the MinIO deployment.
 
-- Replace :mc-cmd:`PATH <mc ilm ls ALIAS>` with the name of the bucket for
+- Replace :mc-cmd:`PATH <mc ilm rule ls ALIAS>` with the name of the bucket for
   which to retrieve the configured lifecycle management rules.