Right now, the extension is hardcoded to look in the ~/.zowe folder for profiles. This is not ideal.
There should be some sort of mechanism for the extension. At the very least it could also look for the zowe environment variable to determine where profiles are stored. A further item could be added to have vs code look for a config file in a project directory / user settings directory. This file could work similar to how the markdownlint.json, tsconfig.json, or tslint.json works.
If this item is picked up please investigate a solution first and propose back to the CLI squad.
@Colin-Stone Is this function enough to fix this issue? or .zowe should be removed completely?
export function getZoweDir(): string {
ImperativeConfig.instance.loadedConfig = {
defaultHome: path.join(os.homedir(), ".zowe"),
envVariablePrefix: "ZOWE"
};
return ImperativeConfig.instance.cliHome;
}
I was going to suggest speaking to Timothy but he beat me too it with a thumbs up.