Handle config listing before first SRE deployment - #2650
Open
sylvesterkaczmarek wants to merge 2 commits into
Open
Handle config listing before first SRE deployment#2650sylvesterkaczmarek wants to merge 2 commits into
sylvesterkaczmarek wants to merge 2 commits into
Conversation
sylvesterkaczmarek
marked this pull request as ready for review
August 15, 2026 18:41
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
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.
Fixes #2639.
Summary
pulumi.yamlas an empty Pulumi project set when listing SRE configsWhy
dsh config availablecan legitimately run after SHM deployment and config upload but before the first SRE deployment. In that state SRE config blobs exist, whilepulumi.yamlhas not been created yet. Loading it unconditionally raises an Azure storage error and produces a traceback.Using the existing
from_remote_or_createpath preserves normal behavior when the file exists and yields an empty deployed-project set when it does not.Testing
A focused command regression test was added. The full repository test suite was not executed locally, so this is opened as a draft for CI validation.