Skip to content

Commit 9d16b69

Browse files
authored
docs: Document that atespace names must not be reused (agent-substrate#3450)
Concurrency tests in agent-substrate#3255 showed that a request authorized against a deleted atespace can apply to a new atespace with the same name. A previous owner can regain `owner` on it or delete it. We decided not to fix this in code. Atespace names must not be reused, and nothing enforces it. This documents the limitation in the authorization guide and qualifies the claim that a recreated atespace starts with no policy. I used an AI assistant to analyze the issue and draft the doc text, and reviewed the result. --------- Signed-off-by: Shruti Nair <[email protected]>
1 parent fd576d3 commit 9d16b69

1 file changed

Lines changed: 10 additions & 1 deletion

File tree

‎docs/guides/authorization.md‎

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -275,7 +275,9 @@ kubectl ate --token-file me.token delete access-policy -a team-a
275275
since.
276276
- The global policy can't be deleted; update it with no bindings instead.
277277
- Deleting an atespace deletes its policy, so a recreated atespace starts
278-
with none.
278+
with none. A request authorized against the old atespace and still in
279+
flight across the delete and recreate can apply to the new one. See
280+
[Known limitations](#known-limitations).
279281
- Changes take effect on the next call.
280282

281283
## Recovering access
@@ -311,6 +313,13 @@ For a shared cluster, beyond replacing the default bootstrap owner:
311313

312314
## Known limitations
313315

316+
- **Atespace names must not be reused.** Grants are keyed by atespace name,
317+
and calls are authorized before the write runs. If an atespace is deleted
318+
and recreated under the same name, a request authorized against the old
319+
atespace and still in flight across the delete and recreate can land on
320+
the new one, including granting access to it or deleting it. Nothing
321+
enforces unique names. Once an atespace is deleted, don't create another
322+
one under that name; use a fresh name instead.
314323
- **Tags can copy an actor's data.** A tag is a durable copy of an actor's
315324
memory and disk, including secrets, and outlives the actor. Any atespace
316325
editor can tag, publish and clone any actor in the atespace.

0 commit comments

Comments
 (0)