Feature #57161
Check for sealed config files before deploying
Status: | New | Start date: | 2014-03-21 | |
---|---|---|---|---|
Priority: | Could have | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | - | |||
Target version: | - |
Description
When your config files are sealed, you get an error from the CopyConfiguration task, which is run very late in the deployment. This might ruin a complete deployment when you forgot to decrypt the config files, so it's probably better to check for it early in the deployment (probably in a pre-deployment check)