This message was deleted.

sparse-intern-71089

10/20/2021, 1:11 PM

This message was deleted.

prehistoric-activity-61023

10/20/2021, 1:28 PM

not really sure what you want to achieve but if you just want to use pulumi to configure LOCAL k8s cluster, you can use local state backend

prehistoric-activity-61023

10/20/2021, 1:28 PM

see: https://www.pulumi.com/docs/intro/concepts/state/#logging-into-the-local-filesystem-backend

fast-florist-41572

10/20/2021, 1:30 PM

Thanks @prehistoric-activity-61023 that's what I suspected. Its just cumbersome as people will need to login and logout depending on what you are doing. The idea is to have consistency with deployments. Whether I deploy yaml/helm to a local env vs our staging and prod. I would prefer it either all uses pulumi or not

prehistoric-activity-61023

10/20/2021, 1:31 PM

do you want to deploy the same project to local envs as well as staging/prod?

prehistoric-activity-61023

10/20/2021, 1:32 PM

I think you can specify the state backend in

Pulumi.yaml

file but I’m not sure you can do the same on stack level.

prehistoric-activity-61023

10/20/2021, 1:33 PM

https://www.pulumi.com/docs/reference/pulumi-yaml/ (see the

backend

parameter)

prehistoric-activity-61023

10/20/2021, 1:33 PM

another option I’d check, I’m pretty sure it was possible to override this using env variable

prehistoric-activity-61023

10/20/2021, 1:33 PM

so in case of local development, I’d wrap this in a shell script that would use that env var

fast-florist-41572

10/20/2021, 1:34 PM

Ah awesome, that could actually work nicely. Let me give that a try thanks

prehistoric-activity-61023

10/20/2021, 1:35 PM

see https://www.pulumi.com/docs/reference/cli/environment-variables/ (

PULUMI_BACKEND_URL

)

prehistoric-activity-61023

10/20/2021, 1:36 PM

so normally you will use Pulumi Service (or other remote state backend of your choice)

prehistoric-activity-61023

10/20/2021, 1:37 PM

and in case of local development you’d use:

Copy code

PULUMI_BACKEND_URL=file://./local-state.json pulumi up -s local

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.