This message was deleted.

Do I have to check in the produced yaml files after the provisioning process?

You will in general need to ensure you persist the stack files (

Pulumi.<stackname>.yaml

) for each stack, as these are where config is stored and shared. For long lived stacks/branches, it is typical to check these in to source control. For short-lived stacks (perhaps like feature branch stacks), you could chose to not check them in, and use a combination of

pulumi stack init

,

pulumi config set

, and

pulumi config refresh

from within your feature branch automation to manage the stack config. You can see an example of doing this sort of thing in the Pulumify implementation: https://github.com/pulumi/actions-pulumify/blob/master/infra/pulumify#L82-L131

Is the produced 

encryptkey

 import?

The

encryptedkey

is important if you have any secret config. I am actually not sure off the top of my head whether this gets downloaded by

pulumi config refresh

. Ideally it does, in which case the above process would work as is. If it doesn't, then you may need to store this separately. (though if you find that to be the case, please do also open an issue in GitHub - I believe we should be able to support retrieving this from

pulumi config refresh

).