Skip to main content

cloud-init operations

v0.1.7

cloud-init introspection + boot diagnostics + stage re-runs. Use when an EC2/GCE/Azure VM finishes booting but the workload didn't come up the way it should: check overall status, blame slow modules, dump user-data / cloud-config / vendor-data as the instance actually saw them, tail the cloud-init logs, and (with operator approval) re-run individual modules or the full init pipeline.

17 allowed by default 5 need approval 1 denied by default
Pack ID
cloud-init
Vendor
emisar
OS
linux
Actions
23
Required binaries. Install these on the host before relying on the pack — an action that calls a missing one fails at run time.
cloud-init

Install

emisar pack install validates the pack and verifies its content hash before copying it into /etc/emisar/packs. The --hash below pins the install to the exact bytes on this page — a tampered copy is rejected. After install, reload the runner; it re-reads the catalog and advertises every action.

content hash: sha256:bb8a5b7a0a07326871e8b286aaab3c1c5daf48bd20497b8b191faedf2ec8af7a

on the runner host
sudo emisar pack install cloud-init \
  --hash sha256:bb8a5b7a0a07326871e8b286aaab3c1c5daf48bd20497b8b191faedf2ec8af7a \
  --dest /etc/emisar/packs

# Reload so the runner re-reads the catalog:
sudo systemctl reload emisar

Actions 23 total

View on GitHub