Skip to content

eds wf app: no way to set env vars, secrets or container resources #24

Open

Description

@Anomalyru

Problem

A Workflow Studio application created with eds wf app create builds the repository's Dockerfile and runs it on Container Apps. Real apps need runtime configuration (a database URL, a secret key, SMTP and S3 credentials), but eds has no way to provide it.

Checked with eds main-868af1c, built from main:

  • eds wf app create and eds wf app update accept only name, branch, port, repository and space. There are no flags for environment variables, secrets, CPU/RAM or min instances.
  • Pipeline variables (eds wf variable create NAME value --pipeline-id …) are substituted into the pipeline only. A variable created this way is absent from the running container, whose environment has only platform variables such as PORT and HOSTNAME.
  • Settings changed by hand on the underlying Container App do not survive eds wf app deploy: the create_container step deletes the container and creates it again (status: running. Deleting… → Creating container … with image …).
  • Resources are fixed: the create_container log shows configuration 0.1vcpu-256mb, and neither app create/update nor app show exposes it.

Request

Something like:

eds wf app create|update <app> --env KEY=VALUE --secret KEY=<secret-manager-ref> \
    --configuration <preset> --min-instances N

stored on the application and applied by create_container on every deploy, with eds wf app show printing the current values (secret values masked).

If a supported way already exists, please document it in README and skills/eds/SKILL.md.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions