imperative
imperative copied to clipboard
Nested profiles not loaded from global config if there is a conflict
With the following config files, the CLI is not able to retrieve information from the default profile.
This behavior is the same regardless of the profile type. (e.g. base
)
Should the CLI be expected to use --zosmf-p zosmf.1
and --zosmf-p zosmf.2
interchangeably?
// project config
{
"$schema": "./zowe.schema.json",
"profiles": {
"zosmf": {
"profiles": {
"2": {
"type": "zosmf",
"properties": {
"basePath": "/ibmzosmf/api/v1/"
}
}
}
}
},
"defaults": {
// "zosmf": "zosmf.2" // no default zosmf profile specified
}
}
// global config
{
"$schema": "./zowe.schema.json",
"profiles": {
"zosmf": {
"profiles": {
"1": {
"type": "zosmf",
"properties": {
"basePath": "/ibmzosmf/api/v1/"
}
}
}
}
},
"defaults": {
"zosmf": "zosmf.1"
}
}