* Adding perpetual wiggle test to reproduce exclude/include case
* Making PerpetualWiggleStorageMigration pass reliably
* Add improvement for initializing storage server using new perpetual_wiggle_storage_engine config
* Making PerpetualWiggleStorageMigration test pass more reliably
* Remove debugging notes
* Add PerpetualWiggleStorageMigrationWorkload documentation.
* Add documentation for perpetual_storage_wiggle_engine config
* Improve PerpetualWiggleStorageMigration reliability
Right now this only allows one server address being excluded. This is useful
when the database is unavailable but we want the recruitment to skip some
particular processes.
Manually tested the concept works with a loopback cluster.
* Encryption data at-rest db-config
Description
diff-1: Handle 'force' updates to encryption_at_rest db-config
Major changes proposed:
1. Introduce 'encryption_data_at_rest_mode" 'configure new'
option to enable Encryption data at-rest. The feature is disabled
by default.
2. The configuration is meant to be set at the time of database
creation, addition checks will be done to avoid updating the config
in subsequent PR.
3. DatabaseConfiguration validity check to account for "tenant_mode"
set to `required` if Encryption data at-rest is selected given
EncryptionDomain matches Tenant boundaries.
Testing
devCorrectness - 100K
