Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[next] Nested option (optionDefinitions) issues #1908

Open
zFernand0 opened this issue Dec 7, 2021 · 0 comments
Open

[next] Nested option (optionDefinitions) issues #1908

zFernand0 opened this issue Dec 7, 2021 · 0 comments
Labels
bug Something isn't working priority-medium Not functioning - next quarter if capacity permits severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.

Comments

@zFernand0
Copy link
Member

  1. ConfigSchema APIs may not support nested options
    In ConfigSchema.parseSchema function...
    https://github.com/zowe/imperative/blob/cae116c8995e358a5e21ef00c3347ecf47689509/packages/config/src/ConfigSchema.ts#L115

  2. Programmers may not be able to defined nested secure properties.
    For example:
    banana.origin.country = USA could be in plain text, but plugin developers may want to secure banana.origin.token = secret.
    However, they have to secure the entire object (banana.origin = ****)
    https://github.com/zowe/imperative/blob/1210bcd5d46045492764fa5f13070a64529556e7/__tests__/src/packages/profiles/src/constants/ProfileInfoConstants.ts#L84-L100

  3. Users may be able to define nested secure properties.
    https://github.com/zowe/imperative/blob/1210bcd5d46045492764fa5f13070a64529556e7/__tests__/src/packages/profiles/src/constants/ProfileInfoConstants.ts#L107-L130
@zFernand0 zFernand0 added the team-profile Issues and PRs related with the team config initiative label Dec 7, 2021
@zFernand0 zFernand0 added this to the Backlog milestone Dec 7, 2021
@zFernand0 zFernand0 added bug Something isn't working priority-medium Not functioning - next quarter if capacity permits severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex. and removed team-profile Issues and PRs related with the team config initiative labels Mar 7, 2023
@zFernand0 zFernand0 self-assigned this Mar 7, 2023
@zFernand0 zFernand0 added the v3 prospective changes for v3 label Sep 6, 2023
@zFernand0 zFernand0 modified the milestones: Backlog, Zowe V3 Sep 6, 2023
@zFernand0 zFernand0 removed their assignment Sep 6, 2023
@awharn awharn transferred this issue from zowe/imperative Nov 13, 2023
@JTonda JTonda removed the v3 prospective changes for v3 label Feb 14, 2024
@adam-wolfe adam-wolfe removed this from the Zowe V3 milestone Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working priority-medium Not functioning - next quarter if capacity permits severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.
Projects
Zowe CLI Squad
Status: Medium Priority
Milestone
No milestone
Development

No branches or pull requests
3 participants
@JTonda @zFernand0 @adam-wolfe