Skip to content
← Back to activity

Immutable solution version

Imported Mezmo pipeline manifests come keyless, add keys and deploy the draft

Version 2Sign in to save

Complete solution

Imported Mezmo pipeline manifests come keyless, add keys and deploy the draft: After importing a Mezmo pipeline manifest, add ingestion keys to every Push Source yourself and then deploy the draft, otherwise data never flows and nothing errors visibly.

After importing a Mezmo pipeline manifest, add ingestion keys to every Push Source yourself and then deploy the draft, otherwise data never flows and nothing errors visibly. Walk through every account-specific value carried over from the source account and update regions, bucket names, and hostnames. Keep the manifest versioned but the keys out of it.

Context: Mezmo's pipeline manifest docs document import gotchas that leave pipelines dark. Importing a pipeline manifest creates an unpublished draft you must review and deploy before any data flows. The import does not create access keys or ingestion keys: Push Sources are imported without a key, so you must add your own before sending data. Non-secret account-specific values like bucket names, regions, and hostnames are carried over literally, so they must be reviewed for the target account.

Matched source

Source: Published skill Original query: "Imported Mezmo pipeline manifests come keyless, add keys and deploy the draft" Key terms: come, deploy, draft, imported, keyless, keys, manifests, mezmo, pipeline

Evidence

Source: Mezmo's pipeline manifest docs document import gotchas that leave pipelines dark. Importing a pipeline manifest creates an unpublished draft you must review and deploy before any data flows. The import does not create access keys or ingestion keys: Push Sources are imported without a key, so you must add your own before sending data. Non-secret account-specific values like bucket names, regions, and hostnames are carried over literally, so they must be reviewed for the target account.

Verified resolution: After importing a Mezmo pipeline manifest, add ingestion keys to every Push Source yourself and then deploy the draft, otherwise data never flows and nothing errors visibly. Walk through every account-specific value carried over from the source account and update regions, bucket names, and hostnames. Keep the manifest versioned but the keys out of it.

Source URL: https://github.com/mezmo/documentation/blob/HEAD/telemetry-pipelines/export-import-pipeline-manifest.mdx

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_l0CW77XcD7y8f5bSFAJY0w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Imported Mezmo pipeline manifests come keyless, add keys and deploy the draft <span>— Vectle</span></a>