From ada553c3d2a9d637928bd3360e68cf4e04d9069a Mon Sep 17 00:00:00 2001 From: Andrew Jandacek Date: Mon, 3 Jun 2024 11:46:38 +0200 Subject: [PATCH 01/11] add tables Signed-off-by: Andrew Jandacek --- docs/whats-new/breaking-changes-v3.md | 40 ++++++++++++++++----------- 1 file changed, 24 insertions(+), 16 deletions(-) diff --git a/docs/whats-new/breaking-changes-v3.md b/docs/whats-new/breaking-changes-v3.md index b4c045eb3c..db6643582e 100644 --- a/docs/whats-new/breaking-changes-v3.md +++ b/docs/whats-new/breaking-changes-v3.md @@ -1,33 +1,41 @@ -# Breaking Changes and Important Updates in Zowe v3 +# Important Updates in Zowe v3 The upcoming release of Zowe v3 will bring a range of major changes in Zowe functionality. Review this article for details about changes to various Zowe components to be introduced in Zowe v3. ## API Mediation Layer (API ML) +The following table presents changes to the API Mediation Layer in v3 and if there are any required actions for the API ML user. + ### Breaking Changes to API ML -* Authentication endpoints will not support the route `/api/v1/gateway`, and instead will support only `/gateway/api/v1` -* Spring Enabler will be updated to Spring Boot 3 and Spring 6. Spring Boot 2 and Spring 5 versions will no longer be supported. -* Datasets API will be archived -* Jobs API will be archived -* Metrics service will be archived -* IMS API will be archived -* Java 17 will be required for the API Mediation Layer to run -* z/OSMF in version V2R5 with APAR PH12143 applied -* Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://` +| Change in Zowe v3 | Required action | +|----|-----------------------| +| Authentication endpoints will not support the route `/api/v1/gateway`, and instead will support only `/gateway/api/v1` | ??? | +| Spring Enabler will be updated to Spring Boot 3 and Spring 6. Spring Boot 2 and Spring 5 versions will no longer be supported | ??? | +| Datasets API will be archived | ??? | +| Jobs API will be archived | ??? | +| Metrics service will be archived | ??? | +| IMS API will be archived | ??? | +| Java 17 will be required for the API Mediation Layer to run | ??? | +| z/OSMF in version V2R5 with APAR PH12143 applied | ??? | +| Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://` | ??? | -### Important updates -The current API Gateway contains Authentication and Authorization Services. This service will be separated as a standalone service. This is the only API Mediation Layer service that needs z/OS directly +### Important API ML updates + +The current API Gateway contains Authentication and Authorization Services. This service will be separated as a standalone service. This is the only API Mediation Layer service that needs z/OS directly. ## Application Framework ### Breaking changes -* Updating Angular to Version 16 from Version 12 -* Removing the core-js dependency -* Updating Webpack to version 5 -* Updating Typescript to 4.9 +| Change in Zowe v3 | Required action | +|----|-----------------------| +| Updating Angular to Version 16 from Version 12 | ??? | +| Removing the core-js dependency | ??? | +| Updating Webpack to version 5 | ??? | +| Updating Typescript to 4.9 | ??? | + ## CLI From 0748c65c63a3b9cd054210b88be4d6d09a15b059 Mon Sep 17 00:00:00 2001 From: Andrew Jandacek Date: Tue, 4 Jun 2024 11:09:18 +0200 Subject: [PATCH 02/11] change sidebar from Zowe vNext to Zowe v3 Signed-off-by: Andrew Jandacek --- sidebars.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sidebars.js b/sidebars.js index 18f422ca87..9cac44bcd5 100644 --- a/sidebars.js +++ b/sidebars.js @@ -4,7 +4,7 @@ module.exports = { "whats-new/zowe-announcements", { type: "category", // doc(default), 'link'(external links), 'ref'(page without without sidebar) - label: "Zowe vNext", + label: "Zowe v3", link: {type:"doc", id:"whats-new/breaking-changes-v3"}, items: [ "whats-new/zowe-v3-office-hours", From dedf5fdc3a19cded195493b14f757378e7554063 Mon Sep 17 00:00:00 2001 From: Jakub Balhar Date: Wed, 5 Jun 2024 10:22:32 +0200 Subject: [PATCH 03/11] Add steps to be taken for breaking changes Signed-off-by: Jakub Balhar --- docs/whats-new/breaking-changes-v3.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/whats-new/breaking-changes-v3.md b/docs/whats-new/breaking-changes-v3.md index db6643582e..826d20bdbc 100644 --- a/docs/whats-new/breaking-changes-v3.md +++ b/docs/whats-new/breaking-changes-v3.md @@ -8,18 +8,18 @@ The following table presents changes to the API Mediation Layer in v3 and if the ### Breaking Changes to API ML -| Change in Zowe v3 | Required action | -|----|-----------------------| -| Authentication endpoints will not support the route `/api/v1/gateway`, and instead will support only `/gateway/api/v1` | ??? | -| Spring Enabler will be updated to Spring Boot 3 and Spring 6. Spring Boot 2 and Spring 5 versions will no longer be supported | ??? | -| Datasets API will be archived | ??? | -| Jobs API will be archived | ??? | -| Metrics service will be archived | ??? | -| IMS API will be archived | ??? | -| Java 17 will be required for the API Mediation Layer to run | ??? | -| z/OSMF in version V2R5 with APAR PH12143 applied | ??? | -| Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://` | ??? | - +| Change in Zowe v3 | Required action | +|----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Authentication endpoints will not support the route `/api/v1/gateway`, and instead will support only `/gateway/api/v1` | If you use the endpoints directly, change the URLs to start with `/gateway/api/v1`. If you use ZAAS client to integrate with API Mediation Layer, you don't need to do anything the change is handled in ZAAS client code. | +| Spring Enabler will be updated to Spring Boot 3 and Spring 6. Spring Boot 2 and Spring 5 versions will no longer be supported | Upgrade the extending service based on the Spring Enabler to Spring Boot 3 and Spring 6 | +| Datasets API will be archived | The service was disabled by default in Version 2. If you enable the service via `components.data-sets.enabled: true` and use the APIs documented in [Data sets Swagger](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/datasets.json) you need to move to the usage of the similar z/OSMF endpoints. | +| Jobs API will be archived | The service was disabled by default in Version 2. If you enable the service via `components.jobs.enabled: true` and use the APIs documented in [Jobs Swagger](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/jobs.json) you need to move to the usage of the similar z/OSMF endpoints. | +| Metrics service will be archived | The service was in Technical Preview. Currently there is no replacement, but with V3 the Open Telemetry standard will be implemented that serves as replacement. | +| IMS API will be archived | The service wasn't fully supported, if you were using the API, please reach out to IBM team and consult with them the follow-up steps | +| Java 17 will be required for the API Mediation Layer to run | For V3 you need to update z/OS to at least 2.5 as this brings support of Java 17 and then install Java 17 and provide the path to Java 17 to Zowe java configuration. | +| z/OSMF in version V2R5 with APAR PH12143 applied | If you are running z/OS before 3.1 validate that PH12143 APAR was applied to the z/OSMF installation used by Zowe | +| Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://` | If your zowe configuration contains `safkeyring:////` change this part to `safkeyring://` | +| Support access to the zosmf only via /ibmzosmf route. Supporting both created issues for CLI setup | If you use the zosmf via `{apimlUrl}/zosmf/{zosmfEndpoint}` you need to move to `{apimlUrl}/ibmzosmf/{zosmfEndpoint}` | ### Important API ML updates From 7fecd9804c3b59a00f82ab5d196dfbc1d4bb6f0f Mon Sep 17 00:00:00 2001 From: Andrew Jandacek Date: Thu, 13 Jun 2024 13:11:15 +0200 Subject: [PATCH 04/11] minor language refactor Signed-off-by: Andrew Jandacek --- docs/whats-new/breaking-changes-v3.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/whats-new/breaking-changes-v3.md b/docs/whats-new/breaking-changes-v3.md index 826d20bdbc..02bebdc72d 100644 --- a/docs/whats-new/breaking-changes-v3.md +++ b/docs/whats-new/breaking-changes-v3.md @@ -10,16 +10,16 @@ The following table presents changes to the API Mediation Layer in v3 and if the | Change in Zowe v3 | Required action | |----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Authentication endpoints will not support the route `/api/v1/gateway`, and instead will support only `/gateway/api/v1` | If you use the endpoints directly, change the URLs to start with `/gateway/api/v1`. If you use ZAAS client to integrate with API Mediation Layer, you don't need to do anything the change is handled in ZAAS client code. | -| Spring Enabler will be updated to Spring Boot 3 and Spring 6. Spring Boot 2 and Spring 5 versions will no longer be supported | Upgrade the extending service based on the Spring Enabler to Spring Boot 3 and Spring 6 | -| Datasets API will be archived | The service was disabled by default in Version 2. If you enable the service via `components.data-sets.enabled: true` and use the APIs documented in [Data sets Swagger](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/datasets.json) you need to move to the usage of the similar z/OSMF endpoints. | +| Authentication endpoints will not support the route `/api/v1/gateway`, and instead will support only `/gateway/api/v1` | If you use the endpoints directly, change the URLs to start with `/gateway/api/v1`. If you use ZAAS client to integrate with API Mediation Layer, no action is required as the change is handled in the ZAAS client code. | +| Spring Enabler will be updated to Spring Boot 3 and Spring 6. Spring Boot 2 and Spring 5 versions will no longer be supported | Upgrade the extending service based on the Spring Enabler to Spring Boot 3 and Spring 6. | +| Datasets API will be archived | This service was disabled by default in Version 2. If you enable the service via `components.data-sets.enabled: true` and use the APIs documented in [Data sets Swagger](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/datasets.json) you need to move to the usage of the similar z/OSMF endpoints. | | Jobs API will be archived | The service was disabled by default in Version 2. If you enable the service via `components.jobs.enabled: true` and use the APIs documented in [Jobs Swagger](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/jobs.json) you need to move to the usage of the similar z/OSMF endpoints. | -| Metrics service will be archived | The service was in Technical Preview. Currently there is no replacement, but with V3 the Open Telemetry standard will be implemented that serves as replacement. | -| IMS API will be archived | The service wasn't fully supported, if you were using the API, please reach out to IBM team and consult with them the follow-up steps | -| Java 17 will be required for the API Mediation Layer to run | For V3 you need to update z/OS to at least 2.5 as this brings support of Java 17 and then install Java 17 and provide the path to Java 17 to Zowe java configuration. | -| z/OSMF in version V2R5 with APAR PH12143 applied | If you are running z/OS before 3.1 validate that PH12143 APAR was applied to the z/OSMF installation used by Zowe | -| Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://` | If your zowe configuration contains `safkeyring:////` change this part to `safkeyring://` | -| Support access to the zosmf only via /ibmzosmf route. Supporting both created issues for CLI setup | If you use the zosmf via `{apimlUrl}/zosmf/{zosmfEndpoint}` you need to move to `{apimlUrl}/ibmzosmf/{zosmfEndpoint}` | +| Metrics service will be archived | The service was in Technical Preview. Currently there is no replacement. In V3, the Open Telemetry standard will be implemented that serves as a replacement. | +| IMS API will be archived | The service was not fully supported. If you were using the API, please reach out to the IBM team for follow-up steps. | +| Java 17 will be required for the API Mediation Layer to run | For V3, it is necessary to update z/OS to version 2.5 or later as this brings support of Java 17. It is necessary to install Java 17 and provide the path to Java 17 to Zowe J ava configuration. | +| z/OSMF in version V2R5 with APAR PH12143 applied | If you are running a version of z/OS before 3.1, validate that PH12143 APAR was applied to the z/OSMF installation used by Zowe | +| Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://` | If your Zowe configuration contains `safkeyring:////`, change this part to `safkeyring://` | +| Support access to z/OSMF only via /ibmzosmf route. Supporting both created issues for CLI setup | If you use z/OSMF via `{apimlUrl}/zosmf/{zosmfEndpoint}` you need to move to `{apimlUrl}/ibmzosmf/{zosmfEndpoint}` | ### Important API ML updates From 83c275a20a57864f89dd245618f0b6f5b159dcd8 Mon Sep 17 00:00:00 2001 From: adam-wolfe <122040687+adam-wolfe@users.noreply.github.com> Date: Thu, 20 Jun 2024 15:16:07 -0400 Subject: [PATCH 05/11] Add CLI and VSC Explorer tables Signed-off-by: adam-wolfe <122040687+adam-wolfe@users.noreply.github.com> --- docs/whats-new/breaking-changes-v3.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/docs/whats-new/breaking-changes-v3.md b/docs/whats-new/breaking-changes-v3.md index 02bebdc72d..18c841b4ee 100644 --- a/docs/whats-new/breaking-changes-v3.md +++ b/docs/whats-new/breaking-changes-v3.md @@ -41,9 +41,11 @@ The current API Gateway contains Authentication and Authorization Services. This ### Breaking changes -* Introducing a new format for error messages to improve clarity -* Removing V1 profile support -* Removing deprecated items - [CLI](https://github.com/zowe/zowe-cli/issues/1694) and [Imperative](https://github.com/zowe/zowe-cli/issues/1873) +| Change in Zowe v3 | Required action| +|-|-| +|Introducing a new format for error messages to improve clarity|Adjust Zowe CLI scripts that parse error messages to handle the new error format| +|Removing V1 profile support|Implement a team configuration or use Zowe CLI's built-in V1 profile conversion command: `zowe config convert`| +|Removing deprecated items - [CLI](https://github.com/zowe/zowe-cli/issues/1694) and [Imperative](https://github.com/zowe/zowe-cli/issues/1873)|Zowe CLI extenders or users of the Zowe Client Node.js SDK will need to review the breaking changes and adjust their code to account for removed/changed classes, functions, and constants| ### Pre-release availability @@ -63,10 +65,12 @@ The current API Gateway contains Authentication and Authorization Services. This ### Breaking changes -* Removing V1 profile support -* Removing deprecated items - [Explorer for VSCode](https://github.com/zowe/zowe-explorer-vscode/issues/2238) +| Change in Zowe v3 | Required action| +|-|-| +|Removing V1 profile support|Implement a team configuration or use Zowe Explorer's built-in V1 profile conversion functionality| +|Removing deprecated items - [Explorer for VSCode](https://github.com/zowe/zowe-explorer-vscode/issues/2238)|Zowe Explorer extenders or users of the Zowe Explorer APIs will need to review the breaking changes and adjust their code to account for removed/changed classes, functions, and constants| +|Storing extension settings in local storage|Settings and history previously stored in the .vscode settings folder will no longer be available. Users will have to adjust their Zowe Explorer settings after updating to V3| * Changing profile creation menus -* Storing extension settings in local storage ### Important updates From ba2c187b687157b8f1f4ae833f52a7774416143c Mon Sep 17 00:00:00 2001 From: adam-wolfe <122040687+adam-wolfe@users.noreply.github.com> Date: Fri, 21 Jun 2024 09:56:14 -0400 Subject: [PATCH 06/11] Removed profile mgmt breaking change for ze Signed-off-by: adam-wolfe <122040687+adam-wolfe@users.noreply.github.com> --- docs/whats-new/breaking-changes-v3.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/whats-new/breaking-changes-v3.md b/docs/whats-new/breaking-changes-v3.md index 18c841b4ee..83eab3db63 100644 --- a/docs/whats-new/breaking-changes-v3.md +++ b/docs/whats-new/breaking-changes-v3.md @@ -70,7 +70,6 @@ The current API Gateway contains Authentication and Authorization Services. This |Removing V1 profile support|Implement a team configuration or use Zowe Explorer's built-in V1 profile conversion functionality| |Removing deprecated items - [Explorer for VSCode](https://github.com/zowe/zowe-explorer-vscode/issues/2238)|Zowe Explorer extenders or users of the Zowe Explorer APIs will need to review the breaking changes and adjust their code to account for removed/changed classes, functions, and constants| |Storing extension settings in local storage|Settings and history previously stored in the .vscode settings folder will no longer be available. Users will have to adjust their Zowe Explorer settings after updating to V3| -* Changing profile creation menus ### Important updates From 055c950fc96e839083fed12a2488f33d999de002 Mon Sep 17 00:00:00 2001 From: anaxceron Date: Thu, 1 Aug 2024 15:21:08 -0400 Subject: [PATCH 07/11] Ana edits Signed-off-by: anaxceron --- docs/whats-new/breaking-changes-v3.md | 20 +++++++++----------- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/docs/whats-new/breaking-changes-v3.md b/docs/whats-new/breaking-changes-v3.md index 83eab3db63..4ccae131d3 100644 --- a/docs/whats-new/breaking-changes-v3.md +++ b/docs/whats-new/breaking-changes-v3.md @@ -1,14 +1,14 @@ -# Important Updates in Zowe v3 +# Important Updates in Zowe V3 -The upcoming release of Zowe v3 will bring a range of major changes in Zowe functionality. Review this article for details about changes to various Zowe components to be introduced in Zowe v3. +The upcoming release of Zowe V3 brings a range of major changes in Zowe functionality, including *breaking changes*, or modifications that require updates to avoid disruptions in your applications. -## API Mediation Layer (API ML) +Review this article for details about changes to various Zowe components to be introduced in Zowe V3, and any actions required you might need to take. -The following table presents changes to the API Mediation Layer in v3 and if there are any required actions for the API ML user. +## API Mediation Layer (API ML) -### Breaking Changes to API ML +### Breaking changes -| Change in Zowe v3 | Required action | +| Change in Zowe V3 | Required action | |----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Authentication endpoints will not support the route `/api/v1/gateway`, and instead will support only `/gateway/api/v1` | If you use the endpoints directly, change the URLs to start with `/gateway/api/v1`. If you use ZAAS client to integrate with API Mediation Layer, no action is required as the change is handled in the ZAAS client code. | | Spring Enabler will be updated to Spring Boot 3 and Spring 6. Spring Boot 2 and Spring 5 versions will no longer be supported | Upgrade the extending service based on the Spring Enabler to Spring Boot 3 and Spring 6. | @@ -20,7 +20,6 @@ The following table presents changes to the API Mediation Layer in v3 and if the | z/OSMF in version V2R5 with APAR PH12143 applied | If you are running a version of z/OS before 3.1, validate that PH12143 APAR was applied to the z/OSMF installation used by Zowe | | Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://` | If your Zowe configuration contains `safkeyring:////`, change this part to `safkeyring://` | | Support access to z/OSMF only via /ibmzosmf route. Supporting both created issues for CLI setup | If you use z/OSMF via `{apimlUrl}/zosmf/{zosmfEndpoint}` you need to move to `{apimlUrl}/ibmzosmf/{zosmfEndpoint}` | - ### Important API ML updates The current API Gateway contains Authentication and Authorization Services. This service will be separated as a standalone service. This is the only API Mediation Layer service that needs z/OS directly. @@ -29,19 +28,18 @@ The current API Gateway contains Authentication and Authorization Services. This ### Breaking changes -| Change in Zowe v3 | Required action | +| Change in Zowe V3 | Required action | |----|-----------------------| | Updating Angular to Version 16 from Version 12 | ??? | | Removing the core-js dependency | ??? | | Updating Webpack to version 5 | ??? | | Updating Typescript to 4.9 | ??? | - ## CLI ### Breaking changes -| Change in Zowe v3 | Required action| +| Change in Zowe V3 | Required action| |-|-| |Introducing a new format for error messages to improve clarity|Adjust Zowe CLI scripts that parse error messages to handle the new error format| |Removing V1 profile support|Implement a team configuration or use Zowe CLI's built-in V1 profile conversion command: `zowe config convert`| @@ -65,7 +63,7 @@ The current API Gateway contains Authentication and Authorization Services. This ### Breaking changes -| Change in Zowe v3 | Required action| +| Change in Zowe V3 | Required action| |-|-| |Removing V1 profile support|Implement a team configuration or use Zowe Explorer's built-in V1 profile conversion functionality| |Removing deprecated items - [Explorer for VSCode](https://github.com/zowe/zowe-explorer-vscode/issues/2238)|Zowe Explorer extenders or users of the Zowe Explorer APIs will need to review the breaking changes and adjust their code to account for removed/changed classes, functions, and constants| From 7e0add2f38119754dabcde043a06b7a0b841f0df Mon Sep 17 00:00:00 2001 From: Andrew Jandacek Date: Tue, 13 Aug 2024 16:53:40 +0200 Subject: [PATCH 08/11] reformat App Framework section Signed-off-by: Andrew Jandacek --- docs/whats-new/breaking-changes-v3.md | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/docs/whats-new/breaking-changes-v3.md b/docs/whats-new/breaking-changes-v3.md index 4ccae131d3..99cc500ce6 100644 --- a/docs/whats-new/breaking-changes-v3.md +++ b/docs/whats-new/breaking-changes-v3.md @@ -16,7 +16,7 @@ Review this article for details about changes to various Zowe components to be i | Jobs API will be archived | The service was disabled by default in Version 2. If you enable the service via `components.jobs.enabled: true` and use the APIs documented in [Jobs Swagger](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/jobs.json) you need to move to the usage of the similar z/OSMF endpoints. | | Metrics service will be archived | The service was in Technical Preview. Currently there is no replacement. In V3, the Open Telemetry standard will be implemented that serves as a replacement. | | IMS API will be archived | The service was not fully supported. If you were using the API, please reach out to the IBM team for follow-up steps. | -| Java 17 will be required for the API Mediation Layer to run | For V3, it is necessary to update z/OS to version 2.5 or later as this brings support of Java 17. It is necessary to install Java 17 and provide the path to Java 17 to Zowe J ava configuration. | +| Java 17 will be required for the API Mediation Layer to run | For V3, it is necessary to update z/OS to version 2.5 or later as this brings support of Java 17. It is necessary to install Java 17 and provide the path to Java 17 to Zowe Java configuration. | | z/OSMF in version V2R5 with APAR PH12143 applied | If you are running a version of z/OS before 3.1, validate that PH12143 APAR was applied to the z/OSMF installation used by Zowe | | Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://` | If your Zowe configuration contains `safkeyring:////`, change this part to `safkeyring://` | | Support access to z/OSMF only via /ibmzosmf route. Supporting both created issues for CLI setup | If you use z/OSMF via `{apimlUrl}/zosmf/{zosmfEndpoint}` you need to move to `{apimlUrl}/ibmzosmf/{zosmfEndpoint}` | @@ -24,17 +24,6 @@ Review this article for details about changes to various Zowe components to be i The current API Gateway contains Authentication and Authorization Services. This service will be separated as a standalone service. This is the only API Mediation Layer service that needs z/OS directly. -## Application Framework - -### Breaking changes - -| Change in Zowe V3 | Required action | -|----|-----------------------| -| Updating Angular to Version 16 from Version 12 | ??? | -| Removing the core-js dependency | ??? | -| Updating Webpack to version 5 | ??? | -| Updating Typescript to 4.9 | ??? | - ## CLI ### Breaking changes @@ -49,6 +38,15 @@ The current API Gateway contains Authentication and Authorization Services. This * V3 pre-release versions are available via [npm](https://www.npmjs.com/package/@zowe/cli?activeTab=readme) under the 'next' tag +## Application Framework + +### Breaking changes + +* Updating Angular to Version 16 from Version 12 +* Removing the core-js dependency +* Updating Webpack to version 5 +* Updating Typescript to 4.9 + ## Explorer for Intellij ### Important updates From 0d612f8e59ea17ea5240603b5f316422e6ecf0f2 Mon Sep 17 00:00:00 2001 From: Andrew Jandacek Date: Tue, 13 Aug 2024 16:54:44 +0200 Subject: [PATCH 09/11] fix title Signed-off-by: Andrew Jandacek --- docs/whats-new/breaking-changes-v3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/whats-new/breaking-changes-v3.md b/docs/whats-new/breaking-changes-v3.md index 99cc500ce6..75bba33dc7 100644 --- a/docs/whats-new/breaking-changes-v3.md +++ b/docs/whats-new/breaking-changes-v3.md @@ -1,4 +1,4 @@ -# Important Updates in Zowe V3 +# Important updates in Zowe V3 The upcoming release of Zowe V3 brings a range of major changes in Zowe functionality, including *breaking changes*, or modifications that require updates to avoid disruptions in your applications. From 0e6e122f7c7795e56e297de619f0afbd4e24eb8a Mon Sep 17 00:00:00 2001 From: Andrew Jandacek Date: Mon, 19 Aug 2024 14:19:45 +0200 Subject: [PATCH 10/11] language clean up Signed-off-by: Andrew Jandacek --- docs/whats-new/breaking-changes-v3.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/whats-new/breaking-changes-v3.md b/docs/whats-new/breaking-changes-v3.md index 75bba33dc7..57a95c5f20 100644 --- a/docs/whats-new/breaking-changes-v3.md +++ b/docs/whats-new/breaking-changes-v3.md @@ -11,18 +11,18 @@ Review this article for details about changes to various Zowe components to be i | Change in Zowe V3 | Required action | |----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Authentication endpoints will not support the route `/api/v1/gateway`, and instead will support only `/gateway/api/v1` | If you use the endpoints directly, change the URLs to start with `/gateway/api/v1`. If you use ZAAS client to integrate with API Mediation Layer, no action is required as the change is handled in the ZAAS client code. | -| Spring Enabler will be updated to Spring Boot 3 and Spring 6. Spring Boot 2 and Spring 5 versions will no longer be supported | Upgrade the extending service based on the Spring Enabler to Spring Boot 3 and Spring 6. | -| Datasets API will be archived | This service was disabled by default in Version 2. If you enable the service via `components.data-sets.enabled: true` and use the APIs documented in [Data sets Swagger](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/datasets.json) you need to move to the usage of the similar z/OSMF endpoints. | -| Jobs API will be archived | The service was disabled by default in Version 2. If you enable the service via `components.jobs.enabled: true` and use the APIs documented in [Jobs Swagger](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/jobs.json) you need to move to the usage of the similar z/OSMF endpoints. | -| Metrics service will be archived | The service was in Technical Preview. Currently there is no replacement. In V3, the Open Telemetry standard will be implemented that serves as a replacement. | +| Spring Enabler will be updated to Spring Boot 3 and Spring 6. Spring Boot 2 and Spring 5 versions will no longer be supported | Upgrade extending services based on the Spring Enabler to Spring Boot 3 and Spring 6. | +| Datasets API will be archived | This service was disabled by default in Version 2. If you enable the service via `components.data-sets.enabled: true` and use the APIs documented in [Data sets Swagger](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/datasets.json), it is necessary to move to the usage of the similar z/OSMF endpoints. | +| Jobs API will be archived | The service was disabled by default in Version 2. If you enable the service via `components.jobs.enabled: true` and use the APIs documented in [Jobs Swagger](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/zowe/docs-site/docs-staging/api_definitions/jobs.json), it is necessary to move to the usage of the similar z/OSMF endpoints. | +| Metrics service will be archived | The service was in Technical Preview. Currently there is no replacement. In V3, the Open Telemetry standard will be implemented, which will serve as a replacement. | | IMS API will be archived | The service was not fully supported. If you were using the API, please reach out to the IBM team for follow-up steps. | | Java 17 will be required for the API Mediation Layer to run | For V3, it is necessary to update z/OS to version 2.5 or later as this brings support of Java 17. It is necessary to install Java 17 and provide the path to Java 17 to Zowe Java configuration. | -| z/OSMF in version V2R5 with APAR PH12143 applied | If you are running a version of z/OS before 3.1, validate that PH12143 APAR was applied to the z/OSMF installation used by Zowe | -| Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://` | If your Zowe configuration contains `safkeyring:////`, change this part to `safkeyring://` | -| Support access to z/OSMF only via /ibmzosmf route. Supporting both created issues for CLI setup | If you use z/OSMF via `{apimlUrl}/zosmf/{zosmfEndpoint}` you need to move to `{apimlUrl}/ibmzosmf/{zosmfEndpoint}` | +| z/OSMF in version V2R5 with APAR PH12143 applied | If you are running a version of z/OS before 3.1, validate that the PH12143 APAR was applied to the z/OSMF installation used by Zowe. | +| Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://`. | If your Zowe configuration contains `safkeyring:////`, change this part to `safkeyring://`. | +| Support access to z/OSMF only through `/ibmzosmf` route. V3 will not support access through the `/zosmf` route.| If you use z/OSMF via `{apimlUrl}/zosmf/{zosmfEndpoint}` you need to move to `{apimlUrl}/ibmzosmf/{zosmfEndpoint}.` | ### Important API ML updates -The current API Gateway contains Authentication and Authorization Services. This service will be separated as a standalone service. This is the only API Mediation Layer service that needs z/OS directly. +The current API Gateway contains the Authentication and Authorization Service. This service will be separated as a standalone service. The Authentication and Authorization Service is the only API ML service that directly requires z/OS. ## CLI From f443224390116ffd7c36b8062a1e942a8b2383eb Mon Sep 17 00:00:00 2001 From: Andrew Jandacek Date: Mon, 19 Aug 2024 14:23:20 +0200 Subject: [PATCH 11/11] fix punctuation Signed-off-by: Andrew Jandacek --- docs/whats-new/breaking-changes-v3.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/whats-new/breaking-changes-v3.md b/docs/whats-new/breaking-changes-v3.md index 57a95c5f20..99966a3ed7 100644 --- a/docs/whats-new/breaking-changes-v3.md +++ b/docs/whats-new/breaking-changes-v3.md @@ -18,8 +18,8 @@ Review this article for details about changes to various Zowe components to be i | IMS API will be archived | The service was not fully supported. If you were using the API, please reach out to the IBM team for follow-up steps. | | Java 17 will be required for the API Mediation Layer to run | For V3, it is necessary to update z/OS to version 2.5 or later as this brings support of Java 17. It is necessary to install Java 17 and provide the path to Java 17 to Zowe Java configuration. | | z/OSMF in version V2R5 with APAR PH12143 applied | If you are running a version of z/OS before 3.1, validate that the PH12143 APAR was applied to the z/OSMF installation used by Zowe. | -| Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://`. | If your Zowe configuration contains `safkeyring:////`, change this part to `safkeyring://`. | -| Support access to z/OSMF only through `/ibmzosmf` route. V3 will not support access through the `/zosmf` route.| If you use z/OSMF via `{apimlUrl}/zosmf/{zosmfEndpoint}` you need to move to `{apimlUrl}/ibmzosmf/{zosmfEndpoint}.` | +| Configuration of keyrings will require transformation from `safkeyring:////` to `safkeyring://` | If your Zowe configuration contains `safkeyring:////`, change this part to `safkeyring://`. | +| Support access to z/OSMF only through `/ibmzosmf` route. V3 will not support access through the `/zosmf` route | If you use z/OSMF via `{apimlUrl}/zosmf/{zosmfEndpoint}` you need to move to `{apimlUrl}/ibmzosmf/{zosmfEndpoint}.` | ### Important API ML updates The current API Gateway contains the Authentication and Authorization Service. This service will be separated as a standalone service. The Authentication and Authorization Service is the only API ML service that directly requires z/OS.