Skip to content

Since 2.3.3 secrets doesn't work with "env" provider #1852

@abylon-io

Description

@abylon-io

Hi @yottahmd,

The simple yaml

name: main-test2
description: Test2

secrets:
  - name: SMTP_PASSWORD
    provider: env
    key: SECRET_SMTP_PASS

crashes with the error message :

time=2026-03-24T14:06:41.225Z level=INFO msg="Resolving secrets" name=main-test2 run-id=019d202b-4a38-7620-b4e6-5a41affe2ac4 attempt-id=20591e count=1
time=2026-03-24T14:06:41.227Z level=ERROR msg="Failed to initialize DAG execution" name=main-test2 run-id=019d202b-4a38-7620-b4e6-5a41affe2ac4 attempt-id=20591e dag=main-test2 run-id=019d202b-4a38-7620-b4e6-5a41affe2ac4 err="failed to resolve secrets: failed to resolve secret \"SMTP_PASSWORD\" from provider \"env\": environment variable \"SECRET_SMTP_PASS\" is not set"

The same YAML file works perfectly with version 2.3.1 and earlier (since my environment variable SECRET_SMTP_PASS is correctly defined in my .bashrc).
Perhaps I’ve missed a significant change to how ‘secrets’ are managed with the ‘env’ provider.

Many thanks for your help.

Metadata

Metadata

Assignees

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