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 configno longer manages app settings (Imperative & CLI)
fail-on-errordefault 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.mDecodedefaults to true so any plugin with custom RestClient implementation that adds gzip decompression may break
The return value for PluginManagementFacility.requirePluginModuleCallbackchanged.
Common usage: ConfigurationLoader.load
this.pluginNmForUseInCallback = pluginName
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)
tokenValuewere combined into
authTokenand we later reverted this change (Imperative & CLI)
zowe configgroup renamed:
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.jsonwill be broken, adapt them to write to
TranslationServiceetc.) to 12 (
L10TranslationServiceetc.). 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|
|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.
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.
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"
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.
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)
Cross-version compatibility may be possible but is not guarenteed; recommend upgrading both
Existing (V1) APIs will continue to work