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.

Pulumi Community

Config is for changing the way the code works. Config.set would amount to self-modifying code.

No, there is no Config.set. Config is read-only within the context of a Pulumi program.

ok. I want to store variables to a stack. How can I do it??

I suppose it depends on the context. Where do you want to be able to retrieve this value?

I am provisioning postgres. I put table definitions in a folder:
00-initialize.sql
01-update1.sql
02-update2.sql
and execute them from code.

I want to store the number such as 02. so when next time I run pulumi up if I see a new file
03-xxx.sql
04-xxx.sql
I will execute them

otherwise I will skip files already excuted.

You can do it in a Pulumi program, but you've got to write that sort of code yourself.

If you want to store it, you can either manually set it in your config, or write it to a vault or similar.

But ideally, you would use a different tool/library to do that, one better suited to the job.

did “vault” here mean something like aws.appconfig ?

Like SSM Parameters, Hashicorp Vault, or any other persistent cloud-based store for values.

gotch. I will check them. Thank you so much!!!