ibash commented 1 week ago

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When copying an object via the S3 protocol, and specifying a new content-type, the object is not updated with the new content type.

To Reproduce

Upload an object to supabase storage with content-type "text/plain"
Overwrite the object via the s3 protocol, but specify an alternative content type like "audio/mp4"

import { S3Client, CopyObjectCommand } from "@aws-sdk/client-s3";

const client = new S3Client({
  forcePathStyle: true,
  region: "us-west-1",
  endpoint: "supabase-s3-endpoint",
  credentials: {
    accessKeyId: process.env.ACCESS_KEY_ID,
    secretAccessKey: process.env.SECRET_ACCESS_KEY,
  },
});

const bucket = 'my-bucket'
const key = 'my-key.m4a'

const command = new CopyObjectCommand({
  Bucket: bucket,
  CopySource: `${bucket}/${key}`,
  Key: key,
  ContentType: 'audio/mp4'
});

const data = await client.send(command);

console.log('data is ', data)

Expected behavior

After copying the object, the new object should have an update content-type. If you check via curl or via the supabase ui you'll see the content-type has not changed.