Secure properties from non-existent files are not deleted

[t1m0thyj]

When the zowe config secure command is run to save secure properties for a config file, then properties from any other config files that are non-existent are removed from the properties object stored in the vault.

Is this desired behavior? What if a config file is on a network share that sometimes is unavailable?

[awharn]

Something to consider: if a file was deleted, and we didn't remove secure properties for a non-existent file, when would those properties be removed from the credential vault?

It's a complicated situation, and there may need to be more thought on what the desired behavior is here, and how to handle the many different situations.

[t1m0thyj]

Updated issue title to reflect current behavior - secure properties from non-existent config files are not deleted.

I think this is a low priority issue for now since no one has complained, but in the future we may need to pick an approach:

• When updating secure properties in the vault, remove properties for config files that no longer exist. This could cause problems if some paths on the file system exist intermittently like mounted network shares.
• Offer a separate command to prune secure properties. Otherwise, the current behavior leads to storing a JSON object that will continually grow in size every time someone creates a new config file and never shrinks.
  • Perhaps adding a --prune option to the zowe config secure command would make more sense than a separate command - thanks @gejohnston for the idea 🙂