-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forward all extra properties to the SDK calls #2399
Comments
Thank you for raising this enhancement request. |
I see the PR where they are all updated to latest needed at the time and all packages seem updated. closing issue |
That PR definitely helps in this regard (i.e. making it easier to pass any non-schema properties to the corresponding SDKs). We can forward them as needed when/if someone asks for them (for example having a profile with a bunch of dataset allocation attributes like in Step 2 of Dan's blog |
Is your feature request related to a problem? Please describe.
With the ability to store any property in your team-config profiles, we would want Zowe Explorer to be able to send those properties to the z/OSMF requests (similar to how the CLI does it).
Describe the solution you'd like
A single entrypoint for all SDK calls (ideally exposed to extenders via the zowe-explorer-api) that determines which extra properties need to be sent/forwarded to the corresponding z/OSMF requests
Describe alternatives you've considered
Modify every registered command in Zowe Explorer that calls the mainframe in order to pass any extra properties.
Additional Context
After some discussion in the Zowe Explorer standup (Nov 8th, 2022) we decided to go with the following approach:
ProfileInfo
APIs to return all values in the profileProfileInfo: Add support for any properties specified in
zowe.config.json
imperative#899Originally posted by @zFernand0 in #1667 (comment)
The text was updated successfully, but these errors were encountered: