This message was deleted.
# generals
sparse-intern-71089
11/16/2023, 1:53 AMThis message was deleted.
l
little-cartoon-10569
11/16/2023, 4:43 PMSo you can change them. It's a plain text file that you can view and edit. When you edit it, you know you have to deploy afterwards: it has the same priority as your source code.
The state file is not (supposed to be) editable, and it represents what Pulumi has already pushed to the cloud. It's a record of what was done in the past. If you change that, then you've changed what Pulumi thanks has happened in the past, as opposed to what Pulumi plans to change in the future.
b
brash-finland-19802
11/16/2023, 10:32 PMyeah i guess in my head config was state that was associated with a stack
brash-finland-19802
11/16/2023, 10:33 PMwhereas you can have different configs for the same stack
l
little-cartoon-10569
11/17/2023, 12:15 AMNo, you can't. Config is stack level.
little-cartoon-10569
11/17/2023, 12:15 AMIn pseduocode:
Copy code
state = deploy_to_cloud(config, code);little-cartoon-10569
11/17/2023, 12:18 AMConfig goes in to Pulumi; state comes out of Pulumi. You can't edit state: Pulumi does that. If you edit state, nothing happens and state is wrong. If you edit config then deploy, then state is updated by Pulumi and is right (because it reflects changes that Pulumi has made to the cloud).
b
brash-finland-19802
11/17/2023, 5:31 AMi guess what i’m saying is if i have secret values i was hoping i could set it directly in the state
brash-finland-19802
11/17/2023, 5:31 AMthat way it doesn’t depend on an extra config file
l
little-cartoon-10569
11/17/2023, 5:45 AMYou can create a simple custom resource and put the value in there. Mark the value as a secret and it'll be encrypted in state. That would be fine. How would you get the value into state though? You wouldn't want to hard code it in your project file, I think?
little-cartoon-10569
11/17/2023, 5:47 AMOr you could fetch it from somewhere else, like a vault or SSM parameters or equivalent.
little-cartoon-10569
11/17/2023, 5:47 AMBut you cannot write directly to state. The only way to write to state is via
pulumi uplittle-cartoon-10569
11/17/2023, 5:49 AMState is not a config file. The Pulumi config file is a config file: state is a database of deployed resources.
b
brash-finland-19802
11/17/2023, 6:08 AMyeah i’m aware of state as a concept, have done a lot of work with iac tool internals
ultimately though a separate config file is effectively two pieces of state
we currently do use SSM and was wondering about creating a custom resource instead
l
little-cartoon-10569
11/17/2023, 6:46 AMNo, config is not another piece of state: it's another source code file.
You could create a custom resource. I don't know how you'd get the value in, though: your options are in source code, in config, or manually put into a vault or other cloud storage. Source code has the advantage of good review cover (PRs etc.) but it doesn't make encryption of config values easy; a vault is good for encryption but not so great for getting other devs to review changes; config files offer both advantages.