novox/hq issue 153, ADR 0112. 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 mesh-controller #176's branch). On an adopted machine the assignment says accesses: {<id>: <path>} and the mount follows.
Merge after mesh-controller #176 is running. The running controller parses accesses strictly and refuses the id field at registration (checked with module check under both binaries).
novox/hq issue 153, ADR 0112. 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 mesh-controller #176's branch). On an adopted machine the assignment says `accesses: {<id>: <path>}` and the mount follows.
**Merge after mesh-controller #176 is running.** The running controller parses accesses strictly and refuses the `id` field at registration (checked with `module check` under both binaries).
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
novox/hq issue 153, ADR 0112. 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 mesh-controller #176's branch). On an adopted machine the assignment saysaccesses: {<id>: <path>}and the mount follows.Merge after mesh-controller #176 is running. The running controller parses accesses strictly and refuses the
idfield at registration (checked withmodule checkunder both binaries).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.