Skip to content

feat: node-aware bucket and storage dialogs - #124

Merged
St4NNi merged 9 commits into
feat/v3from
feat/node-aware-storage
Nov 13, 2026
Merged

St4NNi merged 9 commits into
feat/v3from
feat/node-aware-storage

Conversation

@St4NNi

@St4NNi St4NNi commented Nov 13, 2026

Copy link
Copy Markdown
Member

A group's S3 storage, its rule for new buckets and its links live on one node. The portal now says which node does what, so a new bucket gets its storage rule and a link goes to the node that can take it.

  • "Link an S3 bucket" lists the realm's nodes. Only a node that holds both the Aruna bucket and the same storage can be picked; the others say why. The node is chosen automatically once the bucket is known, and a node picked by hand stays chosen while it still works. The link and its first sync go to the chosen node.
  • On a node that holds the bucket but lacks the storage, "Add storage" opens the storage dialog for that node with the storage's type, endpoint and root locked to the source; only the region and credentials are entered. If the source storage gets new buckets with a bucket rule, the node takes the same rule when it has no default yet; an existing default is kept unless the user opts in to replace it.
  • "New bucket" lists the nodes as option rows and says what a bucket gets on each: its own S3 bucket on the group storage, or a plain Aruna bucket. The node with the rule is preselected, and Create waits until every node has answered.
  • A storage's root prefix counts as part of its identity, as on the node.

@St4NNi
St4NNi merged commit 2e8dad1 into feat/v3 Nov 13, 2026
1 check passed
@St4NNi
St4NNi deleted the feat/node-aware-storage branch November 13, 2026 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant