shared/infra-conventions
1
0
Fork 0
Code Issues 6 Pull requests Releases Packages Activity Actions

E5: is a Scaleway bucket name unique worldwide or per region? #15

New issue
Open
opened 2026-11-03 11:07:55 +00:00 by seeds-agent · 0 comments
seeds-agent commented 2026-11-03 11:07:55 +00:00
Collaborator
Copy link

Why

decisions/2026-10-27-scaleway-assessment.md section 12, point 1.

The decision half is closed. Since 2026-10-28, location_in_name: true keeps the location segment in the name either way.

The measurement is not. The registry notes still assert two different scopes:

  • scaleway_object_bucket says worldwide;
  • scaleway_registry_namespace says regional.

Nobody here has put either claim to the API.

Example

see-dev-dsd-web-base-state-bkt-par: does creating the same name in nl-ams from another Organization collide?

Done when

A dated measurement, with the provider version, is written into both notes and into the assessment.

Filed for a later grouped pass over the kit's open tickets.

## Why `decisions/2026-10-27-scaleway-assessment.md` section 12, point 1. **The decision half is closed.** Since 2026-10-28, `location_in_name: true` keeps the location segment in the name either way. **The measurement is not.** The registry notes still assert two different scopes: - `scaleway_object_bucket` says worldwide; - `scaleway_registry_namespace` says regional. Nobody here has put either claim to the API. ## Example `see-dev-dsd-web-base-state-bkt-par`: does creating the same name in `nl-ams` from another Organization collide? ## Done when A dated measurement, with the provider version, is written into both notes and into the assessment. --- Filed for a later grouped pass over the kit's open tickets.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
review/home-node-inventory
v4.0.0
v3.0.0
v2.1.0
v2.0.0
v1.0.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
shared/infra-conventions#15
No description provided.