Joe I think you are muted
I believe the extra steps needed for APF is best approach. Reason - I suspect most clients prefer APF manual steps to be reviewed and approved by client security associates.
i joined late, but are you asking if something closer to a one button install would be good, my reply is, "yes." and since i'm in an acf2 shop, any help there would help too. it took us months to get to acf2 configured so zowe-cli worked correctly.
SAMPLIB is the logical place to put it
It's easier to make a second/third try on JCL than a script.
the SAMPLIB/LOADLIB idea also seems to resonate with the Rocket admins
Anyone want to use a z/OSMF workflow to manage the install and config?
Is it in the long term vision that end users of the Zowe Desktop can use a catalog and install additional apps on demand?
i would love to use z/osmf workflow or something similar to install generally.
Any plans to have an IBM assigned 3 letter component ID for Zowe server to prefix message IDs, etc.
lapjo01: Catalog=yes, but user-installed apps... I think it's premature for security reasons. However, we were investigating if users can have a sandbox such that they can use apps that others don't have. Would love to get feedback & collaboration on the subject of app installation to determine best technologies, administration, user experience. It's not what we're doing with CUPID, but it's on the TO-DO list.
Paul, ZWE is the 3-letter code assigned to Zowe.
Paul Newton: We are planning to have ZWE prefix and defined additional characters for other components
The installation changes appear to help, but I would like to see test cases
The current plan about message prefixes is described at https://github.com/zowe/zlc/blob/master/process/messageManagement.md
Especialy, example curl queries that could be used to confirm the correct operation of each of the supported ports.
William, do you mean just a simple post-install check or a more extensive pipeline?
Keep up the great work guys, looks like a good path to go down. Exciting stuff coming.
I thnk both
The first could be used to confirm each of the components are installed correctly
The second could be used by developers as part of their development process
Especially as you already have the three example plugins in the install directory
OK, I think that's a good idea too. We're getting more tests that get automatically run at time of pull request for development's sake, but for the users & installers, some script that invokes curl for sanity tests sounds convenient
For dev testing, one thing that's done manually & in the pipeline is to run "npm run test", for a plugin, which runs unit tests that exist for that app.
how about starting the main task first and that it inturn start the others when sucessful
This was built on Tomcat correct?
If I remember correctly that already has a plugin manager
That is the idea
Hi can we get this presentation
I got an email form IBM