FileLocationS3: support overriding the host/port for an endpoint
In some reported cases, the s3 port used by the gateway may differ from the port in the location endpoint. It could also happen with the host, where a given endpoint would be accessed through a mirror, or with an internal url.
The proposed solution is to allow overriding the host and/or the port for a given enpoint configuration entry.
It would look like:
file-location:
s3:
"minio.example.com:9002":
access-key: myaccesskey
secret-key: mysecretkey
ssl: true
host: minio
port: 9000