pulumi/pkg/backend
Matt Ellis db18ee3905 Retain the SecretsManager that was used to deserialize a deployment
We have many cases where we want to do the following:

deployment -> snapshot -> process snapshot -> deployment

We now retain information in the snapshot about the secrets manager
that was used to construct it, so in these round trip cases, we can
re-use the existing manager.
2019-05-10 17:07:52 -07:00
..
display Encrypt secret values in deployments 2019-05-10 17:07:52 -07:00
filestate Retain the SecretsManager that was used to deserialize a deployment 2019-05-10 17:07:52 -07:00
httpstate Don't track a stack's configuration file in the backend 2019-05-10 17:07:52 -07:00
state Add license headers 2018-05-22 15:02:47 -07:00
apply.go Don't print error prefix when a confirmation prompt is declined 2019-03-26 15:17:18 -07:00
backend.go Don't return serialized outputs from stack.GetRooStacktResource 2019-05-10 17:07:52 -07:00
backend_test.go Refactor config loading out of the backend 2019-05-10 17:07:52 -07:00
snapshot.go Retain the SecretsManager that was used to deserialize a deployment 2019-05-10 17:07:52 -07:00
snapshot_test.go Retain the SecretsManager that was used to deserialize a deployment 2019-05-10 17:07:52 -07:00
stack.go Remove backend.GetStackCrypter 2019-05-10 17:07:52 -07:00
updates.go Add detection of Azure Pipelines (#2705) 2019-05-07 11:49:13 -07:00