stack72 30c8718098 Using a decryptAll functionality when deserializing a deployment ... Fixes: #6445 Previously, when a deserialisation operation, e.g, `pulumi stack` command was carried out, each service based secret in the stack was decrypted one at a time causing n times the number of API requests to the Pulumi service This meant the following to the user: ``` Calling [pulumi stack] with [1000] secrets took [210.04] seconds. ``` With this new code, we now scan all the inputs and outputs for secrets, and make a bulk secret decryption dequest to the service and then use the secrets as a lookup for the deserialization operation. This means we have a single API request to the service and now means the following to the user: ``` Calling [pulumi stack] with [1000] secrets took [16.30] seconds. ```		2022-01-04 13:32:13 +00:00
..
manager.go	Using a decryptAll functionality when deserializing a deployment	2022-01-04 13:32:13 +00:00