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

Zowe config auto-init with default values from profile definition #2164

Open
sosadchuk opened this issue May 31, 2024 · 1 comment
Open

Zowe config auto-init with default values from profile definition #2164

sosadchuk opened this issue May 31, 2024 · 1 comment
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have

Comments

@sosadchuk
Copy link

Hi Zowe CLI team,

I wanted to request an enhancement to the auto-init feature: make newly created profiles use defaults from the profile definition.

Currently, after invoking config auto-init, I get a profile like the following:

"bcmdbmdsz": {
    "type": "dbm-db2",
    "properties": {
        "basePath": "/bcmdbmdsz/api/v1"
    }
},

This profile is not ready to be used due to missing CLI plugin-specific properties, and requires manual edits.

However when I use just config init, the dbm-db2 profile is created with defaults:

"dbm-db2": {
    "type": "dbm-db2",
    "properties": {
        "port": 7300,
        "environmentList": {
            "ssid1": "env1@host1:port1",
            "ssid2": "env2@host2:port2"
        },
        "workDatasetPrefix": "${user}.dbmdb2",
        "deleteWorkDatasets": true,
        "overwriteOutputFiles": false,
        "authid": "${user}",
        "sqlid": "${user}",
        "terminationCharacter": ";"
    },
    "secure": [
        "user",
        "password"
    ]
},

What would really be great - is to get is a profile using both information from API ML, and the defaults coming from the profile definition (and I believe the port property has to be removed along with the secure node because this data should be used from the base profile with API ML host, port, and credentials):

"dbm-db2": {
    "type": "dbm-db2",
    "properties": {
        "basePath": "/bcmdbmdsz/api/v1"
        "environmentList": {
            "ssid1": "env1@host1:port1",
            "ssid2": "env2@host2:port2"
        },
        "workDatasetPrefix": "${user}.dbmdb2",
        "deleteWorkDatasets": true,
        "overwriteOutputFiles": false,
        "authid": "${user}",
        "sqlid": "${user}",
        "terminationCharacter": ";"
    }
},

Thanks,
Sergei.

@sosadchuk sosadchuk added enhancement New feature or request new The issue wasn't triaged yet labels May 31, 2024
Copy link

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

@JTonda JTonda added priority-low Legit issue but cosmetic or nice-to-have and removed new The issue wasn't triaged yet labels Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have
Projects
Status: Low Priority
Development

No branches or pull requests

2 participants