Starting from 12/08, the Zowe Onboarding Squad will hold the Office Hours to discuss the details about the upcoming V2 release. More information can be found in the Office Hour section.
The V2 documentation site is available at V2 Docs Site Preview
If you want to learn more about what you can expect compatibility wise, the statement is here
Breaking changes for Zowe CLI end users
zowe config no longer manages app settings (Imperative & CLI)fail-on-error default changed to true for zowe plugins validate (Imperative & CLI)Breaking changes that could prevent a V1 plug-in (or SDK) from working in V2
AbstractRestClient.mDecode defaults to true so any plugin with custom RestClient implementation that adds gzip decompression may breakThe return value for PluginManagementFacility.requirePluginModuleCallback changed. this.requirePluginModuleCallback.bind(this).this.requirePluginModuleCallback(pluginName).
Common usage: ConfigurationLoader.load
Before:
this.pluginNmForUseInCallback = pluginName
ConfigurationLoader.load(null,pkgJsonData,this.requirePluginModuleCallback.bind(this))
After:
pluginConfig = ConfigurationLoader.load(null,pkgJsonData,this.requirePluginModuleCallback(pluginName))
The following changes were marked for deprecation in the zowe-v1-lts release. These changes are also less likely to impact plug-ins.
Breaking changes for Zowe CLI & Imperative plug-in developers (V2-V2 - these changes only impacted early adopters of @next as these are breaking changes made during the technical preview validation phase - thanks to the community for their feedback)
tokenType and tokenValue were combined into authToken and we later reverted this change (Imperative & CLI) zowe config group renamed: --user → --user-config and --global → --global-config
ConfigSchemas.loadProfileSchemas → ConfigSchemas.loadSchema
Config.set no longer coerces string values to other types unless parseString = true (potential SDK impact - not CLI Plug-in impact)
Summary: Major install & configuration simplication due to various improvements. Reduced overhead and increased performance due to reduction in server count, optimised networking, and 64 bit ZSS
Some configuration, such as port and IP values, are different by default but can be reconfigured to old values. But, some app framework extensions may not work in v2 without enhancements.
server.json will be broken, adapt them to write to zowe.yaml insteadTranslationService etc.) to 12 (L10TranslationService etc.). For help in updating your Desktop apps to match new internationalization usage, please reference: Sample Angular App example
All the changes are available here: Box Excel Sheet
Check out the OMP Calendar for specific time of the V2 office hours.
| Date | Topic | Link to the meeting | Link to the recording | Links to the materials |
| 12/08/2021 12PM - 1PM ET | Kickoff | https://zoom.us/j/94312528890 | Zoom recording | Presentation |
| 01/05/2022 12PM - 1PM ET | CLI | https://zoom.us/j/94312528890 | Zoom recording | Presentation |
| 01/12/2022 12PM - 1PM ET | API Mediation Layer | https://zoom.us/j/94312528890 | Zoom recording | Presentation |
| 01/19/2022 12PM - 1PM ET | Explorers | https://zoom.us/j/94312528890 | Zoom recording | Presentation |
| 01/26/2022 12PM - 1PM ET | Web UI (Zowe Application Framework) | https://zoom.us/j/94312528890 | ||
| 02/02/2022 12PM - 1PM ET | Systems / Install | https://zoom.us/j/94312528890 | ||
| 02/09/2022 12PM - 1PM ET | *Optional:* General Information | https://zoom.us/j/94312528890 | ||
| 02/16/2022 12PM - 1PM ET | *Optional:* General Information | https://zoom.us/j/94312528890 | ||
| 02/23/2022 12PM - 1PM ET | General Wrap-up | https://zoom.us/j/94312528890 |
The official date is TBD, the target is Feb 28, 2022; look for the official announcement at Zowe.org landing page announcement banner.
The Zowe Squads have prepared XLS spreadsheets with conformance criteria for all Zowe extensions including: CLI, APIs, App Framework, and Explorerfor VS Code. The spreadsheets clearly show the prior / V1 criteria alongside the new / V2 criteria. Please be aware, there are additions, deletions, and CHANGES to the criteria. In some cases the change is simply that a BEST PRACTICE has been deemed REQUIRED. Use the light-GREEN highlights to easily identify the changes. See the Changes to the Conformance Criteria section at Zowe.org/vNext.
NO. We recommend testing all V1 conformant extensions. See the Coming changes (For Users) section at Zowe.org/vNext.
See the recommendations in the Coming changes section at Zowe.org/vNext.
Obtain the pre-GA Zowe V2 release; for details see the pre-GA Download Availability section at Zowe.org/vNext.
YES, we expect the Zowe V2 Conformance program to be available in early Feb 2022. We will announce when extenders can pre-apply in the LATEST ANNOUNCEMENTS section at Zowe.org/vNext.
All Zowe V1 conformance badges will remain at the Open Mainframe Project Interactive Landscape; we recommend documenting a Zowe compatibility matrix to ensure clients are aware of any/all compatibility issues between your V1 conformant apps and Zowe V2.
Yes, We will announce when extenders can pre-apply in the LATEST ANNOUNCEMENTS section at Zowe.org/vNext.
Anytime. Zowe is an open source project managed by a transparent, open source community.
The V1 LTS Maintenance timeline runs through July 2024. See RELEASE TIMELINE at Zowe.org/download.
You have several options:
You have several options:
Yes. Recordings can be provided on request. Click on the COMMUNITY tab at Zowe.org, navigate to the SLACK box and click #zowe-onboarding and request the recording.
Yes, we plan to introduce a "zowe config convert-profiles" command, which will be available in the v2 release.
This work is still in progress-we are working on a "zowe daemon enable" command to make the daemon installation process as seamless as possible. Daemon mode will be disabled by default, the command must be run to enable it.
The recommended approach for editing the config file is to launch it in VS Code from Zowe Explorer and make modifications there. The designated user responsible for creating and maintaining the config (we recommend a team lead or Administrator) will be able to leverage the built-in “intellisense” when editing the file. Note: Team Config fundamentally changes the paradigm on profile creation & management. Prior to Team Config, all users were required to understand, create, test, trouble-shoot, and manage their own profiles. Team Config was designed to scale all of these tasks back, remove the burden from individual users and centralize it. Once the config is distributed most users should not need to make any significant edits.
Join the discussion on this topic here: https://github.com/zowe/vscode-extension-for-zowe/discussions/1535
No, team config will be reloaded for every command
Team Config will likely support alternates defined in the settings json file, administrators will probably need to hand-edit the configuration file to set a new credential manager
A migration utility is available - it will translate profiles (1 for 1) to new (team config) format AND (optionally) clean-up old profiles and old SCS entries.
Migration to the new profile format is NOT required immediately - the old profiles will work UNLESS a team config is created - that said, the old profiles will not be used if a new team config is available. Simply stated - if a team config is not located, CLI will fall back to using the prior profiles
Yes - CLI can read the old and the new format
Yes (recommend this is cleaned up)
CLI option name is "base-path", property name in config is "basePath"
Yes
The BCM prefix for V2 is required
Yes, this a requirement for V2 conformance, however Pass Tickets can be used and it is possible to leverage the basic authentication to properly participate. The configuration is here: https://docs.zowe.org/stable/extend/extend-apiml/api-mediation-passtickets/#api-services-that-support-passtickets The API ML will issue a passticket for the user when service is accessed as long as the user provides a valid JWT token. We recommend this route (minimally) to give the users a seamless signon experience.
Yes
It is part of your configuration yaml - it is a unique identifier for your service that helps to identify your service and uses the format: companyprefix.productname (Note: it is used for documentation only, has no impact on interacting with API-ML)
TBD
Cross-version compatibility may be possible but is not guarenteed; recommend upgrading both
Existing (V1) APIs will continue to work
Yes
No. Zowe CLI offers more robust functionality for Team Configuration initialization specifically when configuring for MFA/token support, however it is NOT required. Zowe Explorer users interested in configuring for MFA/Tokens can manually update their Team Configuration
No. The Zowe Explorer download experience will not change.
No. Users must plan to convert to the Team Configuration (profiles) format.
The V1-style profiles will remain backward compatible for the duration of the Zowe V2 ACTIVE and MAINTENANCE time period (~4 years), however they will be identified as “deprecated” in Zowe V2 which means they will not be backwards compatible with Zowe V3 and beyond. The same is true for Zowe CLI profiles.
The presence of a Team Configuration renders all V1 profiles unusable. When you opt in to the V2 Team configuration, you cannot revert back.
Yes, as long as there is no team config file present.
Zowe Explorer users may not know. In the CLI, if a V2 profile is found, and a V1 profiles command is issued, an error similar to the following will be displayed:
-> zowe profiles list zosmf
An error occurred trying to list profiles.
Profile IO Error: A Zowe V1 profile operation was attempted with a Zowe V2 configuration in use.
Warning: The command 'profiles list' is deprecated.
Recommended replacement: The 'config list' command
If only V1 profiles exist, the command will work, but a deprecation warning will be displayed:
-> zowe profiles list zosmf
sys1_zosmf
sys2_zosmf (default)
sys3_zosmf
Warning: The command 'profiles list' is deprecated. Recommended replacement: The 'config list' command
Yes, the CLI has a conversion utility. At the present time, Zowe Explorer users who wish to convert over and do not use Zowe CLI will need to create their profiles from scratch OR install Zowe CLI and use the Zowe CLI conversion utility.
Zowe Explorer is available for download at the VisualStudio Marketplace: https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe and the Open VSX Registry: https://open-vsx.org/extension/Zowe/vscode-extension-for-zowe
For Zowe CLI Extensions: the JSON schema file is automatically updated when a Zowe CLI plug-in is installed; more specifically the global schema is dynamically updated -- individual project schemas are not). For Zowe Explorer Extensions: we have plans to automatically insert configuration information into the schema, but at the current time this information will need to be manually added.
For Zowe CLI, the global schema is updated when the new plug-in is installed. New init commands will include the new plug-in profile(s) in the generated zowe.config.json. Project-level schema is not updated at plug-in install time. To update, run zowe config update-schemas. The plan for Zowe Explorer is similar but is still being discussed.
Yes.