This message was deleted.
# dotnets
sparse-intern-71089
12/05/2022, 2:48 PMThis message was deleted.
e
echoing-dinner-19531
12/06/2022, 8:46 AMI don't think there's anything in automation api to change backends. The main approach is to just make sure the ambient login is correct, but I think you can set the Pulumi.yaml for inline programs explicitly and set the backend there (see the ProjectSettings.Backend option)
o
orange-airplane-72526
12/06/2022, 10:44 AMThanks for the info. I'd like to use the s3 backend but am still confused how authentication would be handled when using the Pulumi.yml file?
orange-airplane-72526
12/06/2022, 11:01 AMI think you can set the Pulumi.yaml for inline programs explicitlydo you maybe have an example or docs how to do that?
e
echoing-dinner-19531
12/06/2022, 1:54 PMProjectSettings is the class with the backend property to set.
You then set the workspace settings with the new project settings.
And the workspace settings are what you pass to things like
CreateStackAsyncechoing-dinner-19531
12/06/2022, 1:55 PMauthentication would be handledAuth is always done using ambient environment variables for the s3 backend.
echoing-dinner-19531
12/06/2022, 1:55 PMAlthough you can change them as part of the workspace settings: https://www.pulumi.com/docs/reference/pkg/dotnet/Pulumi.Automation/Pulumi.Automation.LocalWorkspaceOptions.html#Pulumi_Automatio[…]ironmentVariables
o
orange-airplane-72526
12/06/2022, 2:03 PMthats exactly what I was looking for! Thanks!
7 Views