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

What do you mean? As in just having parts of your state missing?

I am currently trying to use the snowflake provider. It looks like in the resource object for the provider, the credentials are also recorded, albeit in encrypted form (`ciphertext` key).

What I'm trying to figure out is: Can Pulumi simply omit the ciphertext from this object? Or is this somehow necessary for its regular function? If I understand correctly, when running Pulumi it pulls credentials from the Pulumi.&lt;stack&gt;.yml file, not the state file.

depending on exactly the operation being done, so yeh it has to be there for things to work correctly in all cases

Out of curiosity, do you know an example where the credential from the state file would be needed?

couple that come to mind:
run a destroy operation outside the project directory
run a replace operation where we need to use the old configuration because the provider says the new configuration can't be used on old resource