Support separate container for CORS settings #422

New issue

Closed

opened 2024-07-08 14:25:17 +00:00 by alexvanin · 1 comment

alexvanin commented

2024-07-08 14:25:17 +00:00

Owner

CORS settings are stored in the container of the bucket, where setting is applied. It is convinient but may affect users metrics such as number and size of objects.

Describe the solution you'd like

As we decided in #42, support optional config parameter for CORS objects. If parameter is set, then use this container to save CORS object. Otherwise keep using container of the bucket.

## Is your feature request related to a problem? Please describe. CORS settings are stored in the container of the bucket, where setting is applied. It is convinient but may affect users metrics such as number and size of objects. ## Describe the solution you'd like As we decided in #42, support __optional__ config parameter for CORS objects. If parameter is set, then use this container to save CORS object. Otherwise keep using container of the bucket.