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.

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

Dynamic config gathering #1899

Open
hizir-bc opened this issue Mar 31, 2022 · 1 comment
Open

Dynamic config gathering #1899

hizir-bc opened this issue Mar 31, 2022 · 1 comment
Labels
community-upvoted enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits

Comments

@hizir-bc
Copy link

hizir-bc commented Mar 31, 2022

Hello,

We need a feature as described below. Can you please check whether it can be possible?

There is a profile section as following below in the zowe.config.json file.

  "foo": {
          "type": "foo",
          "properties": {
              "host": "",
              "protocol": "https",
              "type": "basic",
              "port": 0,
              "basePath": "",
              "strictSSL": false,
              "hlq": "",
              "rejectUnauthorized": false
          },
          "secure": [
              "user",
              "password"
          ]
      }

The requirement is setting this values by commands instead of editing the file directly. It is possible to get this by executing zowe command for each property. Just like zowe config set profiles.lpar1.profiles.foo.properties.host. But this means 8 different command execution.

Can we get a dynamic way similar to zowe config secure command? For example when zowe config set profiles.lpar1.profiles.foo.properties is executed, cli can ask for the values sequentially which are defined in the config file.

Thanks

@t1m0thyj
Copy link
Member

I think this is a really cool idea 🙂 Some more details about the use case that we discussed internally:

  • Supporting the command for higher levels like config set profiles.lpar1.profiles.foo is out of scope.
  • If the properties object is empty, we should prompt for all properties supported by the profile type.
  • If the properties object is populated, we should prompt only for the properties that it includes.

@t1m0thyj t1m0thyj added enhancement New feature or request community-upvoted priority-low Legit issue but cosmetic or nice-to-have labels Nov 29, 2022
@zFernand0 zFernand0 added priority-medium Not functioning - next quarter if capacity permits and removed priority-low Legit issue but cosmetic or nice-to-have labels Mar 8, 2023
@awharn awharn transferred this issue from zowe/imperative Nov 13, 2023
@t1m0thyj t1m0thyj moved this to Medium Priority in Zowe CLI Squad Dec 26, 2023
@adam-wolfe adam-wolfe mentioned this issue Jan 4, 2024
26 tasks
@adam-wolfe adam-wolfe moved this from Medium Priority to PI Backlog in Zowe CLI Squad Feb 8, 2024
@adam-wolfe adam-wolfe mentioned this issue Feb 26, 2024
23 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-upvoted enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits
Projects
Status: PI Backlog
Development

No branches or pull requests

3 participants