zowe config secure - prune option . Is there an API to accomplish this in VSCode Extensions?

[davidkjackson54]

Zowe cli provides the ability to prune obsolete properties from the vault
--prune | -p (boolean)
Delete properties stored in the vault for team config files that do not exist.
Default value: false

Does this capability exist for the VSCode extension user via some api? I haven't found any documentation for this.

[github-actions[bot]]

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

[t1m0thyj]

@davidkjackson54 The "ConfigSecure.rmUnusedProps" API method can be used for this. It is documented in Node.js SDK docs. This API will only update the credentials object in memory, so you may also want to call the "directSave" method afterwards to update the secure credentials stored in the vault. See here for an example of how Zowe CLI does it: https://github.com/zowe/imperative/blob/master/packages/imperative/src/config/cmd/secure/secure.handler.ts#L42-L48

[davidkjackson54]

[t1m0thyj]

@davidkjackson54 ImperativeConfig.instance.config is only defined in the context of Zowe CLI command handlers. In a VS Code extension where you're using the ProfileInfo API, the way to access the config would be profInfo.getTeamConfig() (where profInfo is an instance of the ProfileInfo class).

The directSave API we probably should have made public rather than internal. For now, you could work around this by calling (config.api.secure as any).directSave.

[davidkjackson54]

Hi @t1m0thyj
This works fine:

Is there any possibility that you can make directSave public - it then becomes supported in the future. - rather than an undocumented method..