Apply custom env vars to Automation API workspace#4
Open
jdavredbeard wants to merge 1 commit into
Open
Conversation
The `env()` option was setting `options.custom_env` but those values were
never merged into `_env_vars` or passed to the Automation API. This meant
`env("PULUMI_BACKEND_URL", ...)` had no effect — the workspace would use
whatever backend was ambient, ignoring the caller's intent.
Now custom env vars are:
1. Merged into `_env_vars` (overriding defaults)
2. Passed to `LocalWorkspace(env_vars=...)`
3. Passed to `create_or_select_stack(opts=LocalWorkspaceOptions(env_vars=...))`
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
env()option having no effect — custom env vars were stored inoptions.custom_envbut never merged into_env_varsor passed to the Pulumi Automation APIoptions.custom_envinto_env_varsafter defaults, so custom values take precedenceLocalWorkspace(env_vars=...)andcreate_or_select_stack(opts=LocalWorkspaceOptions(env_vars=...))Without this fix,
env("PULUMI_BACKEND_URL", "file:///tmp/backend")was silently ignored, causing stacks to use the ambient backend (e.g. Pulumi Cloud) instead of the requested file backend.Test plan
test_custom_env_vars_appliedverifying env vars flow through to workspace and stack creation🤖 Generated with Claude Code