minio/internal/bucket/versioning
Harshavardhana 52221db7ef
fix: for unexpected errors in reading versioning config panic (#14994)
We need to make sure if we cannot read bucket metadata
for some reason, and bucket metadata is not missing and
returning corrupted information we should panic such
handlers to disallow I/O to protect the overall state
on the system.

In-case of such corruption we have a mechanism now
to force recreate the metadata on the bucket, using
`x-minio-force-create` header with `PUT /bucket` API
call.

Additionally fix the versioning config updated state
to be set properly for the site replication healing
to trigger correctly.
2022-05-31 02:57:57 -07:00
..
error.go rename all remaining packages to internal/ (#12418) 2021-06-01 14:59:40 -07:00
versioning.go fix: for unexpected errors in reading versioning config panic (#14994) 2022-05-31 02:57:57 -07:00
versioning_test.go fix: multiple fixes in prefix exclude implementation (#14877) 2022-05-07 22:06:44 -07:00