This message was deleted.

sparse-intern-71089

12/05/2022, 2:48 PM

This message was deleted.

echoing-dinner-19531

12/06/2022, 8:46 AM

I 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)

orange-airplane-72526

12/06/2022, 10:44 AM

Thanks 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 AM

I think you can set the Pulumi.yaml for inline programs explicitly

do you maybe have an example or docs how to do that?

echoing-dinner-19531

12/06/2022, 1:54 PM

ProjectSettings 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 CreateStackAsync

echoing-dinner-19531

12/06/2022, 1:55 PM

authentication would be handled

Auth is always done using ambient environment variables for the s3 backend.

echoing-dinner-19531

12/06/2022, 1:55 PM

Although 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

orange-airplane-72526

12/06/2022, 2:03 PM

thats exactly what I was looking for! Thanks!

6 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.