The current tile UI should probably provide a bit more explanation on how the object-endpoint, base-url and repository-endpoint parameters interact.
The preferred method for broker configuration, should probably be the base-url. This allows the user to specify the name of the ECS configured "Base URL", and lookup the actual hostname through the ECS management API.
The object-endpoint is a way to configure the URL directly, without the use of a "Base URL" for situations when the actual URL is not configured in ECS. I think this should be relatively rare, but we ran into it when supporting ECS TestDrive.
The repository-endpoint is a way to override the object endpoint, when the repository bucket is accessible via a different endpoint than the buckets. Again, somewhat rare.
The current tile UI should probably provide a bit more explanation on how the
object-endpoint
,base-url
andrepository-endpoint
parameters interact.The preferred method for broker configuration, should probably be the
base-url
. This allows the user to specify the name of the ECS configured "Base URL", and lookup the actual hostname through the ECS management API.The
object-endpoint
is a way to configure the URL directly, without the use of a "Base URL" for situations when the actual URL is not configured in ECS. I think this should be relatively rare, but we ran into it when supporting ECS TestDrive.The
repository-endpoint
is a way to override the object endpoint, when the repository bucket is accessible via a different endpoint than the buckets. Again, somewhat rare.