Concelier Chromium Connector — Operations Runbook

Last updated: 2026-04-22

Audience: Stella Ops operators running the Concelier Chromium connector.

1. Overview

The Chromium connector ingests Chromium security advisories and maps them to canonical IDs. The canonical runtime source ID is chromium.

2. Authentication

No authentication required for public advisories.

3. Configuration paths

Primary operator path:

Web UI: Security Posture -> Configure Sources or Ops -> Operations -> Feeds & Airgap -> Configure Sources

CLI:

stella db connectors configure chromium \
  --server https://concelier.example.internal \
  --set feedUri=https://mirror.example.internal/chromium/atom.xml

The Chromium connector does not require credentials. Use the UI/CLI configuration path only when overriding the canonical Chrome Releases Atom feed for a mirror or controlled ingestion path.

Compatibility fallback (concelier.yaml):

concelier:
  sources:
    chromium:
      feedUri: "https://chromereleases.googleblog.com/atom.xml"
      initialBackfill: "30.00:00:00"
      windowOverlap: "2.00:00:00"
      maxFeedPages: 4
      maxEntriesPerPage: 50

4. Offline and air-gapped deployments

Mirror the Atom feed and referenced post pages into the Offline Kit.
Repoint feedUri to the mirrored allowlisted endpoint.

5. Common failure modes