Enable a package
Re-enables a disabled package. Enabling a code-carrying package rebuilds with it, synchronously: unlike install, a slot conflict here answers directly with 409 NRY-0006 naming both claimants, since there is no job to poll. A failed build leaves the previous binary intact (NRY-0007). In the rare case the rebuild’s binary swap succeeds but confirming the resulting package row does not, the response is 409 NRY-0017 instead: the change already applies and resolves automatically on the next host restart. A hosted home refuses it 422: a package is compiled and run on the host’s own machine, and an extension registered at an HTTPS address is the hosted way.
Authorizations
Enforced on every transport, with no exempt operation. A person's request — over the default local unix socket exactly as over a TCP listener — must carry a JWT issued by the configured identity provider, which the host verifies itself against that issuer's key set: signature, issuer, expiry, and the person and organisation it names. Requests without a valid one receive 401 NRY-0011. The socket's file permissions are transport and are not an authorisation.
Path Parameters
The package's name.
256Response
The package, now enabled.
An installed package — the one thing a user installs. May carry declarative resources, Go code, or both; only code-carrying packages cost a rebuild.
256True when the package carries Go code and changes require a rebuild.
64The registry reference or local path it was installed from.
1024
