Use a published pack

Add a published pack to one runner. Review its actions and requirements first. Then install a fixed version, provide its credentials, and verify one action.

1. Choose a pack#

Ask the runner which published packs match the host. This command checks pack detection signals such as programs, processes, and ports. It does not install anything.

sudo emisar pack suggest

You can also browse the public pack catalog . Select one pack for the service on this runner.

2. Inspect the pack#

The catalog page shows the current version and content hash. It also lists each action and host requirement. Record the pack ID, version, and full sha256 hash.

3. Install a fixed version#

Use <pack>=<version> to select the published version. Use --hash to require the reviewed bytes. The runner rejects a different hash.

sudo emisar pack install redis=0.2.3 \
  --hash sha256:<full-reviewed-hash>

The command validates the pack and reloads a running runner. A public catalog hash becomes trusted automatically. A custom hash stays pending on Packs.

A private packctl registry uses immutable URLs. Follow Host your own pack registry for that workflow.

4. Configure credentials#

Read the installed pack setup and its live host checks.

sudo emisar pack info redis

1. Install every missing program named by the pack.
2. Put each credential value in /etc/emisar/runner.env.
3. Add each required variable name to execution.inherit_env in /etc/emisar/config.yaml.
4. Run the pack's verification command.
5. Restart the service with sudo systemctl restart emisar.

Keep credential values out of action arguments and pack YAML. See Pack credentials for the complete environment pattern.

5. Verify the pack#

1. Run sudo emisar doctor. Fix every pack error.
2. Open Runners. Confirm that the runner advertises the new actions.
3. Open Packs. Confirm the exact version, hash, and trust state.
4. Run one low-risk read action from the pack.
5. Open Audit. Confirm that the event names the pack, action, runner, and operator.

For a fleet change, use a canary and bounded batches. See Roll out and roll back packs.