fix: handle MissingContentMD5 error from MinIO edge-cicd in setLifecycleRules

MinIO edge-cicd returns MissingContentMD5 for PutBucketLifecycleConfiguration
(requires Content-MD5 header the SDK doesn't always send). Add this error code
to the graceful degradation catch block so lifecycle rules are best-effort on
backends that require this header.

Author: pyramation

packages/bucket-provisioner/__tests__/provisioner.test.ts

@@ -590,6 +590,17 @@ describe('BucketProvisioner — graceful degradation (error-code matching)', ()
     ]);
   });
 
+  it('setLifecycleRules tolerates MissingContentMD5 (MinIO edge-cicd)', async () => {
+    const err = new Error('Missing required header for this request: Content-Md5.');
+    (err as any).name = 'MissingContentMD5';
+    mockSend.mockRejectedValueOnce(err);
+
+    const provisioner = new BucketProvisioner(defaultOptions);
+    await provisioner.setLifecycleRules('test-bucket', [
+      { id: 'test', prefix: '', expirationDays: 1, enabled: true },
+    ]);
+  });
+
   it('setLifecycleRules throws on genuine errors', async () => {
     mockSend.mockRejectedValueOnce(new Error('Network failure'));
 

packages/bucket-provisioner/src/provisioner.ts

@@ -463,15 +463,18 @@ export class BucketProvisioner {
     } catch (err: any) {
       // Some S3-compatible backends (e.g. MinIO edge-cicd) don't support
       // PutBucketLifecycleConfiguration (may require Content-MD5 header
-      // the SDK doesn't send). Treat XML parse errors or "not implemented"
-      // responses as non-fatal.
+      // the SDK doesn't send). Treat XML parse errors, "not implemented",
+      // or missing-header responses as non-fatal.
       if (
         err.Code === 'XmlParseException' ||
         err.name === 'XmlParseException' ||
         err.Code === 'NotImplemented' ||
         err.name === 'NotImplemented' ||
+        err.Code === 'MissingContentMD5' ||
+        err.name === 'MissingContentMD5' ||
         err.message?.includes('not well-formed') ||
         err.message?.includes('not implemented') ||
+        err.message?.includes('Content-Md5') ||
         err.message?.includes('LifecycleConfiguration')
       ) {
         return;