Closed craddm closed 1 year ago
No, this is due to the way that I implemented passing information between stacks. There's an SHM stack and one or more SRE stacks. The SRE stack wants to load some information from the SHM stack. The SHM stack outputs should be available as JSON but it looks like this isn't working. I'll take a look.
I can reproduce this but only when logged into the wrong Pulumi account.
I'd started to guess at this being the reason, as it says I'm logged in to pulumi as deploydsh
. What isn't clear to me is how to make sure I'm logged in to the right pulumi account.
Looking at how Pulumi login is handled https://github.com/alan-turing-institute/data-safe-haven/blob/64a55d832e9a4426bc880a379b9b54193e84dcb3/data_safe_haven/infrastructure/stack_manager.py#L260
Presumably your ability to use the storage account as a backend depends on which AZ account you are authenticated with. Maybe here the dsploydsh
user doesn't have the correct permissions and isn't the user we want to use.
This was due to using an old version of Pulumi. After updating to 3.80.0, which is what the SHM was deployed with, this error doesn't occur.
Possibly because I've missed out something that's required to be supplied as an option to the
dsh deploy sre
command?