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

Support logging in to multiple APIML instances per config file #1705

Closed
Tracked by #1726 ...
t1m0thyj opened this issue Apr 28, 2023 · 3 comments
Closed
Tracked by #1726 ...

Support logging in to multiple APIML instances per config file #1705

t1m0thyj opened this issue Apr 28, 2023 · 3 comments
Labels
enhancement New feature or request keep Issues with this label will be ignored by the stale bot priority-low Legit issue but cosmetic or nice-to-have

Comments

@t1m0thyj
Copy link
Member

Currently we only support logging in to the APIML for base profiles, and there can only be one active base profile per team config file.
If nested profiles like the example below are defined, users may want to log in to multiple APIML instances per team config file.
Either Zowe CLI should also support this scenario with zowe auth login, or we should document it as a known limitation.

{
    "$schema": "./zowe.schema.json",
    "profiles": {
        "lpar1": {
            "profiles": {
                "zosmf": {
                    "type": "zosmf",
                    "properties": {
                        "basePath": "/ibmzosmf/api/v1"
                    }
                }
            },
            "properties": {
                "host": "example1.com",
                "port": 7554,
                "rejectUnauthorized": true,
                "tokenType": "apimlAuthenticationToken"
            },
            "secure": [
                "tokenValue"
            ]
        },
        "lpar2": {
            "profiles": {
                "zosmf": {
                    "type": "zosmf",
                    "properties": {
                        "basePath": "/ibmzosmf/api/v1"
                    }
                }
            },
            "properties": {
                "host": "example2.com",
                "port": 7554,
                "rejectUnauthorized": true,
                "tokenType": "apimlAuthenticationToken"
            },
            "secure": [
                "tokenValue"
            ]
        }
    },
    "defaults": {
        "zosmf": "lpar1.zosmf"
    },
    "autoStore": true
}
@t1m0thyj t1m0thyj added enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have labels Apr 28, 2023
@github-actions
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.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the Stale label Jul 27, 2023
@zFernand0 zFernand0 added keep Issues with this label will be ignored by the stale bot and removed Stale labels Jul 28, 2023
@adam-wolfe adam-wolfe mentioned this issue Sep 27, 2023
20 tasks
@adam-wolfe adam-wolfe mentioned this issue Nov 20, 2023
26 tasks
@t1m0thyj t1m0thyj moved this to Low Priority in Zowe CLI Squad Dec 26, 2023
@adam-wolfe adam-wolfe mentioned this issue Apr 8, 2024
23 tasks
@t1m0thyj
Copy link
Member Author

Zowe CLI may already support this when the --base-profile option is specified on the auth login command.
We should confirm this and document the process if it works.

@github-project-automation github-project-automation bot moved this from Low Priority to Closed in Zowe CLI Squad Sep 3, 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 keep Issues with this label will be ignored by the stale bot priority-low Legit issue but cosmetic or nice-to-have
Projects
Status: Closed
Development

No branches or pull requests

3 participants