search

zowe / zowe-install-packaging

Packaging repository for the Zowe install scripts and files
Eclipse Public License 2.0
26 stars 51 forks source link

Make it clearer updating should occur for new Zowe instances #1243

Open Joe-Winchester opened 4 years ago

Joe-Winchester commented 4 years ago

Customer content

Is your feature request related to a problem? Please describe. Folis installing newer Zowe builds and using pre-existing zowe-instance-directories are not necessarily doing an update, and if they are they are not updating the zowe-runtime directory

Describe the solution you'd like Modify the log messages when a convenience build is installed current is

You must choose an instance directory and create it by running    
'/u/winchj/zowe-1.10.0/install/../runtime/bin/zowe-configure-instance.sh -c <INSTANCE_DIR>'

suggested change to add something like

If you have an existing  <INSTANCE_DIR> created from a previous Zowe runtime you   
must run () to configure it to work with the newer Zowe runtime.      
If you do not have an existing <INSTANCE_DIR> you must choose one and create   
it by running ().

or similar text.

Also,

After zowe-configure-instance.sh is run do a check for the location of where the script is against the ROOT_DIR parameter and issue a warning if they are not the same, to avoid people thinking it is now going to point. Maybe consider a prompt but not sure if this is over cooking it.

stevenhorsman commented 4 years ago

This isn't the correct message Joe. If you are doing an upgrade it says "Check your instance directory is up to date, by running '${ZOWE_ROOT_DIR}/bin/zowe-configure-instance.sh -c '" All this time we’ve said that our principle is that we should treat SMP/E and convenience build the same (ie overwriting the previous install), so why are we changing this now and confusing people?