Confusing behavior when creating gridscale_object_storage_bucket with scoped API tokens

[FloSchick]

Hi there,

Currently, the gridscale_object_storage_bucket resource defaults to the S3 host gos3.io, which corresponds to the fra2 location.

This leads to the following confusing behavior:

If I use an API token scoped to another location (e.g., fra3), the bucket is still created in fra2 if not set in the resource.

This is unexpected because:

• The API token is explicitly scoped to the fra3 project, and I would assume it does not have rights to deploy resources outside of its scope.
• It would be more intuitive if the bucket were created in the same region as the API token’s scope when no S3 host is explicitly set.

Can you clarify if this behavior is intentional or if adjustments are planned to align bucket creation with the API token’s region?

[nvthongswansea]

@FloSchick I will take a look asap.