Convert Plugin from LTS1 to LTS2 - "zowe config convert" of secure profile items #1958
Unanswered
BJostmeyer
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am in the process of changing our Plugin to comply to the new features in Zowe CLI LTS V2.
First time I used "zowe config convert" and see how my existing profile data are copied to the new zowe.config.json. After the conversion I wanted to change user and password for my old profiles and therefore issued the command "zowe config secure".
For my 3 old profiles I was prompted to specify a new password - but it did not ask me for the user, nor did it show me the user that was specified in my old profiles.
However for the zftp plugin (which I also had a profile for) I got a prompt for both - first it asked me for user and then for password.
I guess I figured out why this happened - in my _meta.yaml only password is defined as "secure: true" - not the user. Therefore only the password was in the credential store of V1 - and NOT the user.
Is there any advice how to proceed? Should I simply change my imperative.ts and also make user secure: true - but what about my migrating customers? I think it will confuse them, when they are prompted multiple times for passwords not knowing for which user... more than that - with "zowe config secure" they cannot change/specify both together but only passwords. I think it is unfortunate that we user and password are not strongly kept together as one "credential pair".
Has anybody an advice?
Beta Was this translation helpful? Give feedback.
All reactions