Removal of zosmf profile

[balhar-jakub]

The ibmzosmf static definition was added as part of the cleanup for zosmf to follow the conventions required by conformance. I can't find the exact commit, but the ibmzosmf lived within the context at least as soon as

e27dc32

which is over 4 years ago and the discussion about this is living here: #665

The intention as far as I understand it based on other discussions wasn't to keep these two forever but do the change on the major version boundaries. We missed the opportunity for V2 and as such the intention from our side was to do it on V3 boundary.

[dkelosky]

I think changing zosmf to ibmzosmf service ID is no problem. However, from this zowe/zowe-install-packaging#3708 (comment)

It looks like zosmf (API route) is removed from the URL. I expected to see zosmf/info which is also how I read the conclusion of #665 .

[balhar-jakub]

I believe that there is this confusion:

Currently the zosmf services are available under:
/zosmf/zosmf/info
The newly available zosmf services are available under:
/ibmzosmf/zosmf/info

The issue with keeping both is that it creates invalid zosmf definition if you try to use API ML to autoconfigure z/OSMF and as such we need to retain just one.

This change doesn't impact swagger documentation, it is already coming from the ibmzosmf definition of the z/OSMF

[dkelosky]

What caught my eye was this diff from the tests:

The endpoint to obtain info is zosmf/info, it looks like zosmf is removed. If the only change is from /zosmf/zosmf/info to /ibmzosmf/zosmf/info, I see no problem.

[dkelosky]

Thanks to @balhar-jakub and @achmelo - this test is about a change to the service ID and is not a concern for Zowe CLI and Zowe Explorer. We can close this discussion