Skip to content

fix: pass user-defined env vars to daprd in multi-app run - #1699

Open
magic-peach wants to merge 1 commit into
dapr:masterfrom
magic-peach:fix/multiapp-run-daprd-env
Open

magic-peach wants to merge 1 commit into
dapr:masterfrom
magic-peach:fix/multiapp-run-daprd-env

Conversation

@magic-peach

Copy link
Copy Markdown

Description

GetAppCommand passed config.getEnv() to the app process, but GetDaprCommand never set cmd.Env at all, so env vars set under an app's env key in dapr.yaml never reached the daprd sidecar. This meant the local env secret store, which reads from the sidecar process environment, could never see them. This passes the same user-defined env vars to daprd so the secret store can read them.

Issue reference

Please reference the issue this PR will close: #1361

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests
  • Extended the documentation

GetAppCommand passed config.getEnv() to the app process, but
GetDaprCommand never set cmd.Env at all, so env vars set under an
app's env key in dapr.yaml never reached the daprd sidecar. This
meant the local env secret store, which reads from the sidecar
process environment, could never see them.

Pass the same user-defined env vars to daprd so the secret store can
read them.

Fixes dapr#1361

Signed-off-by: Akanksha Trehun <akankshatrehun@gmail.com>
@magic-peach
magic-peach requested review from a team as code owners September 7, 2026 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Local env secret store can't read env set by Multi-App Run

1 participant