1000TurquoisePogs

This is still an issue people should want to know about for v1. in v2, we state the answer in the zss error codes explanation.

agree but also maybe the page shouldnt even be called 'extending' anymore because some people have put content into it about adding extensions to zowe, which is a user activity...

That and so much more is in the schema https://github.com/zowe/zss/blob/v2.x/staging/schemas/zss-config.json#L216-L352 It'd be good to just get the schemas properly visible. Better than nothing.

Note: if ROOT_DIR occurs anywhere in v2, it should not be replaced with RUNTIME_DIR, which is a v1 thing. For v2, it is instead `zowe.runtimeDirectory`

This is still an issue, for v1

> Include an issue or PR number for each entry. This helps users learn more about the change when needed. This is a little annoying to do since the PR...

Indeed, we used to do this with the zlux cookie (connect.sid.port) before making more use of apimlAuthenticationToken. Maybe we can make this change too.

Keep in mind it's not just apiml. I'm sure nodejs doesnt support the other formats either, and if gskit does, whether zss is doing that properly hasnt been tested.

Good points. I think we need to be careful about 2 things 1. When there are multiple APIML for high availability, the unique prefix/suffix of the cookie should be something...

I am moving this to api-layer to determine what to do. Perhaps this is insightful for the upcoming ID federation.