Closed austince closed 5 months ago
Validated in a local chart change:
Defaulted container "minio" out of: minio, wait-for-available-minio (init)
Start Minio provisioning
Added `provisioning` successfully.
Restart command successfully sent to `provisioning`. Type Ctrl-C to quit or wait to follow the status of the restart process.
┌────────────────┬────────┐
│ HOST │ STATUS │
├────────────────┼────────┤
│ 127.0.0.1:9000 │ ✔ │
└────────────────┴────────┘
Restarted `provisioning` successfully in 564 milliseconds
Bucket created successfully `provisioning/test`.
provisioning/test versioning is enabled
End Minio provisioning
Hi!
Thank you so much for the PR! The team will take a look
Name and Version
bitnami/minio 14.2.1
What architecture are you using?
None
What steps will reproduce the bug?
Are you using any custom parameters or values?
What is the expected behavior?
The provisioning job enables versioning on the bucket.
What do you see instead?
The provisioning job excludes the versioning in standalone mode.
Additional information
It seems as of https://github.com/bitnami/charts/pull/9301#issue-1159940460, versioning was not supported in standalone mode. This is not mentioned in the current docs, and it is possible to configure buckets in standalone mode to be versioned manually.