Use an existing pack Preview

Problem Packs let organizers distribute and host company exercises or problems intended for publication after an event without adding them to the public catalog. Installation stores an immutable revision; Cloud reads activated AWS/CloudFormation packs on the next deployment. Local reads supported problems in its local problems/ tree rather than the Pack store. Publication remains a separate author decision.

Prerequisites

Obtain a trusted local pack directory or HTTPS Git URL plus an immutable full 40-hex commit SHA. Review the declared runtime, files and provenance before installation.

Install the pinned Git revision

make pack-install ARGS="git <https-url> --commit <40-hex-commit-sha>"
make pack-list
bun run pack inspect <id@version>

Run from the repository root. The default store is .tenkacloud/pack-store. Git install uses the network; local-directory validation and installation do not deploy anything.

Verify the stored revision

Check the source, resolved commit and digest. Installation is not authorization to run arbitrary code, expose endpoints or create cloud resources.

Use in a Cloud event

Run from the repository root for Cloud, replacing <id@version> with the manifest ID and version:

bun run pack activate <id@version> --tenant local

local is the fixed selector consumed by the Cloud catalog loader; it does not select Local hosting. Use the default .tenkacloud/pack-store. There is no make pack-activate target. Activation itself performs no AWS operations. Normal Cloud source preparation includes this store in the private source archive and deployment reads the active problem catalog and execution assets. Update between events with make deploy, then select the problem in a new event. Existing events keep their saved catalog. Review runtime and scoring support and rehearse participant solving, scoring and teardown before hosting.

Local does not connect the Pack store to its event catalog. Author supported private Docker/Compose problems in the local problems/ tree, validate them and start with make local. AWS problems run on Cloud. For a private Git repository, obtain an authorized local checkout separately and install that directory. The Pack CLI Git fetcher does not use credentials.