Skip to content

Handle config listing before first SRE deployment - #2650

Open
sylvesterkaczmarek wants to merge 2 commits into
alan-turing-institute:developfrom
sylvesterkaczmarek:fix-config-available-before-sre
Open

Handle config listing before first SRE deployment#2650
sylvesterkaczmarek wants to merge 2 commits into
alan-turing-institute:developfrom
sylvesterkaczmarek:fix-config-available-before-sre

Conversation

@sylvesterkaczmarek

Copy link
Copy Markdown

Fixes #2639.

Summary

  • treat a missing pulumi.yaml as an empty Pulumi project set when listing SRE configs
  • keep showing uploaded SRE configurations before any SRE has been deployed
  • add a regression test for the post-SHM/pre-SRE state

Why

dsh config available can legitimately run after SHM deployment and config upload but before the first SRE deployment. In that state SRE config blobs exist, while pulumi.yaml has not been created yet. Loading it unconditionally raises an Azure storage error and produces a traceback.

Using the existing from_remote_or_create path 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.

@sylvesterkaczmarek
sylvesterkaczmarek marked this pull request as ready for review August 15, 2026 18:41
@sylvesterkaczmarek
sylvesterkaczmarek requested a review from a team as a code owner August 15, 2026 18: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.

After SHM deployment commands generate errors

1 participant