Why is it undefined profiles?
Is this a Zowe Explorer issue, or do you think this is more like a CLI problem on the error being thrown?
Maybe the CLI APIs expected a Binary Name and nothing was provided?
I'd guess that the term undefined should be zowe or bright and what this message says is that the user should type
$ zowe profiles set-default zosmf-profile profilename
It seems we are running into an unintended situation by putting CLI command syntax into error messages in the core code.
This points out a shortcoming of ZE in that the user can't designate a profile to be the default. This came up in a exchange I had with Goran where he'd like a user to work in ZE and then switch to CLI and have commands work seamlessly in the same context. One way to get a measure of that is for the user to designate a connection as the default in ZE and then when switching to the CLI it would just use that same profile.
I guess we could have a better error message instead of undefined profiles?
I'm afraid that default profiles is a concept that may not necessarily apply to the Zowe Explorer as the users need to interact under a certain profile in order to perform an action on a node/object/dataset/job/file.
What will be the purpose of setting a default profile in the Zowe Explorer that users cannot accomplish by adding a search to their favorites?
I believe that CLI users can already leverage context switching from the profile-type options that Imperative provides (i.e. --zosmf-p theAwesomeProfile)
For now, the issue in question could be resolved by providing a better error message.
I agree. to be fair, this happened because I manually deleted my profiles in the .zowe folder. If I deleted it in a correct way then this won't happen.
I agree. to be fair, this happened because I manually deleted my profiles in the .zowe folder. If I deleted it in a correct way then this won't happen.
Since we do not have the means to update/delete profiles yet, I believe handling providing a nicer error message would be Ok for now 馃憤 .
Most helpful comment
I agree. to be fair, this happened because I manually deleted my profiles in the .zowe folder. If I deleted it in a correct way then this won't happen.