An access has an id, and its mounts name it (issue 153) #198

Merged

mesh-admin merged 1 commits from feat/153-an-access-has-an-id into main

2026-09-30 22:07:15 +00:00

Author	SHA1	Message	Date
jschoubben	684b9853ad	An access has an id, and its mounts name it (issue 153) Ten definitions name each access by id; the path stays as the default an assignment may replace, and the host side of every mount says ${access:<id>}. Resolved with no placement, every definition names exactly the paths it named before (TestPlacedDirectoriesKeepTheirPaths, extended). On an adopted machine the assignment now says `accesses: {<id>: <path>}` and the mount follows. Needs the controller that knows an access id (mesh-controller #176); the running one refuses the field at registration.	2026-10-01 00:01:42 +02:00

Author

SHA1

Message

Date

jschoubben

684b9853ad

An access has an id, and its mounts name it (issue 153)

Ten definitions name each access by id; the path stays as the default an assignment may replace,
and the host side of every mount says ${access:<id>}. Resolved with no placement, every definition
names exactly the paths it named before (TestPlacedDirectoriesKeepTheirPaths, extended). On an
adopted machine the assignment now says `accesses: {<id>: <path>}` and the mount follows.

Needs the controller that knows an access id (mesh-controller #176); the running one refuses the
field at registration.

2026-10-01 00:01:42 +02:00