wet-noon-14291
06/17/2020, 2:34 PMbetter-rainbow-14549
06/17/2020, 2:55 PMwet-noon-14291
06/17/2020, 7:05 PMpulumi.<stack>.yaml
would do the trick. I could use the tasks created by pulumi, but I would rather run it from another script I have and the tasks is sort of focused on running pulumi directly.tall-librarian-49374
06/22/2020, 9:43 AMwet-noon-14291
06/22/2020, 10:21 AMservice connection
for it to work from devops? Eitherway, I would expect another error message than what I get if that was the case.rhythmic-finland-36256
06/22/2020, 1:22 PMaz
settings / env vars instead of using the credentials inside the pulumi config? I once had this specific issue when I migrated from the single module for azure to two of them and didn’t take care that I need to specify the az client config twice.azure:
prefix.azuread.Application
this might be an issue and worked before locally because you had a proper az
configuration which is not there in CI/CD.wet-noon-14291
06/23/2020, 12:55 PMrhythmic-finland-36256
06/23/2020, 1:01 PMwet-noon-14291
06/23/2020, 1:14 PMaz login
pulumi.<stack>.yaml
rhythmic-finland-36256
06/23/2020, 1:16 PMdocker run
command”?wet-noon-14291
06/23/2020, 2:02 PMPulumi.dev.yaml
(https://github.com/mastoj/sweetspot/blob/minimal_error/src/infrastructure/Sweetspot.Infrastructure.Application/Pulumi.dev.yaml). That branch only has the relevant code to reproduce to make it easier to reproduce.tall-librarian-49374
06/26/2020, 10:57 AMwet-noon-14291
06/26/2020, 3:27 PM