[BUG]Generate_Keys does not update the namespace, only the config.

[ZAdamMac]

Describe the bug When generating a new key, tapestry will thereafter exhibit one of two behaviours:

• If no older key exists in the keyring, an error will be raised when the key can not be found. This error is handled but causes the script to terminate.
• If an older key exists, that older key is used instead.

This is because generate_keys is correctly updating the configuration, but it's called after parse_config() and therefore needs to be patched to update the NAMESPACE as well.

To Reproduce Steps to reproduce the behavior:

1. Run tapestry with the --genKey flag.

Expected behavior A new key should be generated and written to configuration, and that key should be used throughout the rest of the backup process.

Log/Console Output Where possible, add the output of the Logs or Console when the problem occurs.

Desktop (please complete the following information):

• OS: Only observed on windows to date, but probably on both platforms.

Additional context Add any other context about the problem here.

Bug was reported by the redoubtable Kat Adam-MacEwen

[ZAdamMac]

This will be closed in the 2.0.1 release and the current dev source in the "bug-fixes" branch contains a tested fix.

Slightly premature, but closing as that release will be coming out later today.