You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also, bucket names can be used with a CNAME redirect, which means they need to conform to DNS naming conventions
all the sanitization that happens is a lower(...) but it does not remove . and also doesn't handle the case where the name would be longer than 63 characters etc.
In our case we use a valid DNS name as a bucket name (e.g. host-name.example.com).
This module would then add the label name = host-name.example.com which violates the bucket label constraints.
3e7b600 introduced setting the prefix + name as a bucket label.
However the sanitizing of the name is not complete:
lower(...)
but it does not remove.
and also doesn't handle the case where the name would be longer than 63 characters etc.In our case we use a valid DNS name as a bucket name (e.g.
host-name.example.com
).This module would then add the label
name = host-name.example.com
which violates the bucket label constraints.Steps to reproduce:
Result:
Expected Result:
Solutions:
The text was updated successfully, but these errors were encountered: