Skip to content

feat: environment variable support per runbook #106

Description

@HerbHall

Summary

Allow defining environment variables per runbook that get passed to command execution.

Research Context

  • Task (14.9k stars): .env file loading + per-task env vars
  • Just (31.7k stars): Per-recipe env vars and .env file support
  • mise: Per-task env + tool env configuration

Use Cases

  • Compose files that use ${VAR} substitution
  • Build args: docker build --build-arg VERSION=$VERSION
  • Registry auth: DOCKER_CONFIG pointing to specific credentials
  • Multi-environment: Same command, different env vars for staging vs production

Proposed UX

  • "Environment Variables" section in RunbookFormDialog
  • Key-value pair editor (add/remove rows)
  • Variables passed to docker.cli.exec() environment
  • Optional: Import from .env file

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestpriority:lowNice to have, schedule when convenientresearch-findingFeature ideas from competitive research

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions