- New option with JSON to expire all versions of an object with a delete
marker.
- Changes `mc ilm rule` subcommand flags `--expire-all-object-versions`
to note that only applies to objects without a delete marker.
Closes#1201
A few quick fixes noted in several issues:
- Literal reference in mc batch generate pointed to the wrong include
Closes#1318
- Lingering reference to an "unregister" function removed
Closes#1324
- Adds admonition about root credentials required, even with KES
Closes#1325
- Adds mc batch cancel to list of commands on batch framework overview
page
Closes#1310
- Updates mc client page S3 link to avoid possible copy/paste confusion
Closes#1311
This seems to be a copy error, based on my comparison of the COMPLIANCE
LOCK and S3's Compliance mode (vs S3's Governance mode).
---------
Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
- Updates references for licensing to use "Enterprise" branding
- Updates the mc idp ldap policy entities command with flags and changes
to groups
- Deprecates OpenID envvar
Closes#1271
Closes#1291
Missed a few log lines referencing Operator Console.
Also cleaning up some broken refs and further simplifying references to
the Console when in context of Tenant/MinIO Object Store.
---------
Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
Addresses #1273
# Summary
This pass does three things:
1. Updates all tutorials related to Operator/Tenant deployment for
Kustomize and Helm
2. Removes references to Operator Console + updates to reference
Kustomize/Helm wherever possible
3. Slightly tidies up old or dangling references
This pass does not do these things:
- Link out heavily to Kubernetes docs (for later)
- Clean up organization (singleplat build handles this)
- Addresses OpenShift, Rancher, etc.
---------
Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
Co-authored-by: Allan Roger Reid <allanrogerreid@gmail.com>
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
Updates for mc release 2024-06-20T14-50-54Z
- Adds info about requiring Raw Base64 or Hex keys
- Updates links for KES docs on encryption pages
- Updates encryption pages to use ventilated prose (one sentence per
line)
- Adds new flag for `mc get`
- Updates `mc put` with enc-# flags
Closes#1253
This removes references to version limits and suggests using object
expiration rules to manage unneeded noncurrent versions.
There is no doc issue to track this.
For mc RELEASE.2024-06-10T16-44-16Z
- Updates `mc admin info` to add the `--offline` flag
For MinIO Server RELEASE.2024-06-11T03-13-30Z
- Adds to note to object management page about avoiding the `:`
character on Windows
- Adds info that directory objects (0-byte, end in `/`) do not tier
These releases do not have doc repo issues to track them.
Updates for MinIO Server RELEASE.2024-05-10T01-41-38Z
- Removes references to `MINIO_SERVER_URL` envvar.
- Updates KMS and KES related envvar settings to add KMS as an option.
- Also differentiates KMS and KES related envvar into three groups,
which are mutually exclusive.
Closes#1214
Creates a new object management page to aggregate information on
deleting objects.
Links to the page from other docs throughout.
Intentionally leaves most delete information where it is in existing
docs.
Closes#741
Partially addresses #1190
No staged build unless someone requests it.
# Summary
After some thinking, we've leaned towards just making a note of the
upgrade step and calling it done. We do not typically make extended
discussion of backward-breaking changes at this time, and have no where
to keep that sort of guidance.
Maybe in the future or as part of a larger re-arch we can consider where
we would best keep that kind of guidance.
As far as the rest:
- We are not covering s3zip today, so that's a no-op. We should leave
the ticket open in the event we have bandwidth to document the feature
later
- No changes to Console that need documentation at this time
- Added a quick callout on the warning behavior to the Versioning page
- Metrics v3 is also still In progress, come back to this once the
project is fully baked.
Corrects most references to point to the current command.
Additional references to deprecated command fixed by PR #1198 .
We should merge 1198 at the same time we merge this one.
Admonition added as an include, then put in many files throughout the
docs.
Where it is included, it's the same admonition and text.
It's worth making sure where I placed the include makes sense.
Closes#1186
Updates for server RELEASE.2024-03-30T09-41-56Z
- Adds information that SSE-C encrypted objects can now replicate.
Closes#1177
- Adds information on operator renewal of tenant certificates
Closes#1167
- Corrects a description for `ilm restore` function
Closes#1175
Updates for Console release 0.45.0
- Removes healing references
- Updates headings and subheadings for the current Console UI
Closes#1107
- removes `mc admin obd` command
- moves `mc admin profile` to deprecated list
closes#1164
- Moves wildcard matching from `mc mirror` to `minio-mc.rst` page and
adds ref links throughout as needed.
## Server release RELEASE.2024-03-26T22-10-45Z
- Adding info about node dashboard for Grafana.
- Also updates links to JSON files for other dashboards that were
incorrect.
*no related docs issue*
## Not a server release, but fixes:
- Corrects information about JSON policy file size limits.
- Adds information about limit on tags per object.
Closes#1134
## Server RELEASE.2024-03-21T23-13-43Z
- Adds new `user` envvar and config for REDIS notifications
- Simplifies and updates discussion of encryption keys for SSE
Closes#1169
Adds updates for mc RELEASE.2024-02-24T01-33-20Z
- New `mc put` command
- New `mc get` command
- New `--expire-all-object-versions` flag for the `mc ilm rule add`
command
- Adds info to the expiration of objects in versioned buckets on the
Object Lifecycle Management page
Closes#1140
Adds updates for mc release RELEASE.2024-01-28T16-23-14Z
- adds --skip-errors flag to mc mirror
- updates the mc admin service commands
Closes#1120
MinIO SERVER RELEASE.2024-01-05T22-17-24Z - added new metrics to
github.com/minio/minio for later sync
MinIO SERVER RELEASE.2024-01-28T22-35-53Z - MinIO preallocates memory,
mc update compresses binary in transit MinIO SERVER
RELEASE.2024-02-06T21-36-22Z -
MinIO adds condition key for restricting STS AssumeRoleWithWebIdentity
duration at policy level
Closes#1124 ,
Partially addresses #1116
Partially Addresses #1105
---------
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
Many small fixes:
- Clarify that `mc legalhold set --recursive` applies to current objects
only. Go back and do it again if you want it to apply to newly created
objects.
- Clean up inconsistent capitalization of "legal hold."
- Fix a bunch more `:required:` and `:optional:`
- Add a resync step to the restore site replication instructions
Staged:
http://192.241.195.202:9000/staging/small-clarifications/linux/index.html
# Summary
As per a recent customer issue, our guidance on `MINIO_DOMAIN` and
path/virtual bucket lookups needs some attention.
There are two main areas to address:
1. We need to guide users to avoid namespace collision within the
`MINIO_DOMAIN` , as this causes bucket lookup issues with certain MinIO
services/features
2. We need to generally improve docs on setting `MINIO_DOMAIN` correctly
There is also a side objective from Engineering to ensure we have a
simple admonition to direct users to test wherever possible changes to
config settings before applying to production.
---------
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
# Summary
Closes#1083
Also reorganizes the batch framework pages. Could use additional
refinement, but considering that out of scope for now.
---------
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
In `AssumeRoleWithWebIdentity` requests, the RoleArn form paramter is
designated to specify the role to be assumed. It is crucial to note that
the correct key is RoleArn, not RoleARN.
When I used the "RoleARN" form key instead of "RoleArn," I encountered
an error similar to the following:
```xml
<ErrorResponse xmlns="https://sts.amazonaws.com/doc/2011-06-15/"><Error><Type></Type><Code>InvalidParameterValue</Code><Message>Role arn:minio:iam:::role/dummy-internal does not exist</Message></Error><RequestId>XXX</RequestId></ErrorResponse>
```
Despite this, certain documentation erroneously employs RoleARN. To
rectify this inconsistency, I have replaced the instances of RoleARN
with the correct RoleArn. However, for other documents that use RoleARN
without specifying the form parameter, no modifications have been made.
Ref:
ba245c6c46/cmd/sts-handlers.go (L50C2-L50C12)
