-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No default zosmf profile found for ZOWE CLI #155
Comments
Hey @spufidoo, |
Documentation updated. It is also now possible to create profiles directly from the Zowe Explorer. |
@MikeBauerCA & @jellypuno , it seems that if you start with no profiles in the .zowe > profiles > zosmf folder then the Zowe Explorer won't let you create a new connection. I closed VS Code and I went into that folder and moved out all the contents and then tried to restart then I get this error. This might not be a common case but it doesn't get handled gracefully. I tried again by shutting down, renaming the .zowe folder, and then restarted. This is probably a closer approximation to a totally new user who doesn't have the CLI. In this case, it works - that is I can create new connections. But, I do get the warning about no default profile that I wonder if is necessary because it is mostly creates worry in my mind that I'm already doing things wrong as soon as I begin. |
@jelaplan so based on your error, this is what happened on the background.
One thing that I can tell you is that when I was new in Zowe I don't know about the .zowe folder. So if I needed to remove any profile, I use the CLI command for remove it. Deleting a profile would be a great feature in the Zowe Explorer. It can be added in the roadmap. Regarding the error message, For me, I think it is helpful for total beginners meaning no favorites and no profiles at all. I would be informed of what I should do. But that is just my opinion. |
Sorry if i can created some crazy. A conclusion I have is to eliminate the no default profile message. I think it is a holdover from the days when the Zowe Explorer extension had a dependency on the CLI for profiles. We no longer have that dependency so we don't need the message. I agree that new users won't know about .zowe folder and a delete profiles option in Zowe Explorer is a good idea but also a edit profile option. I know about .zowe and it is a handy way to edit the profiles relative to using the CLI but maybe I'm not as clever as I would like to be because I deleted the _meta file. Issue 319 exists for editing profiles in Zowe Explorer. This feature would make it less desirable to edit the .yaml files directly. |
I am not sure. Maybe @jalel01 can help. Because I remember that we are discussing about this. The scenario is that I'm a new Zowe Explorer User and once I opened the extension then I have no idea what to do. The solution is the no default profile message. |
It isn't uncommon for Web apps to start with a series of tooltips to guide the user. I think Broadcom even has a license for a tool to add this kind of thing. But, those are usually done with subtlety that this message lacks. If you open most apps, desktop or web, they don't prompt you. Consider MS word which doesn't tell you to create or open a document. |
I created issue 332 for deleting a profile. |
|
Trying to install the zowe extension for vscode, I get the following after startup:
No default zosmf profile found for Zowe CLI. A default zosmf profile created with Zowe CLI is required to use the Zowe extension. Please create at least one profile with Zowe CLI.
There is nothing but a zosmf_meta.yaml file in .zowe/profiles/zosmf
What should I put in it?
The text was updated successfully, but these errors were encountered: