Skip to content

Workspace Configuration

Thomas Maerz edited this page Oct 4, 2026 · 1 revision

Workspace Configuration

Slackpipe reads repeated workspace blocks from one secret file:

WORKSPACE=Example Workspace
CHANNEL_URL=https://example-workspace.slack.com
SLACK_TOKEN=<token>
SLACK_COOKIE=<cookie>

Validation

The parser validates:

  • required fields and block completeness;
  • HTTPS Slack workspace URLs;
  • workspace identity and duplicates;
  • token and cookie whitespace/control characters;
  • global settings and boolean values.

Secrets are excluded from object representations and Dagster metadata. Keep the file mode restrictive and mount it read-only.

Identity

WORKSPACE is the stable operator-provided identity used for archive directory naming and workspace metadata. Dagster-safe names are derived separately where identifiers require normalization.

Selection

Workspace selectors are case-insensitive while preserving configured identity. SLACKPIPE_SOLO_WORKSPACES removes selected workspaces from coordinated all-workspace rollouts so operators can run them independently.

Dynamic discovery

The deployment reloader watches the workspace secret for changes and reloads the Slackpipe code location. slackpipe_new_workspace_sensor detects a newly configured workspace and can request its initial ingest job without exposing credentials.

Clone this wiki locally