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

If nsx-t site is not set, alb subcommands will not work. #7

Open
mu853 opened this issue Jul 9, 2022 · 1 comment
Open

If nsx-t site is not set, alb subcommands will not work. #7

mu853 opened this issue Jul 9, 2022 · 1 comment
Assignees

Comments

@mu853
Copy link
Contributor

mu853 commented Jul 9, 2022

alb subcommands should also work outside of the nsx-t environment

$ nsxctl show alb-cloud
2022/07/09 20:27:02 site '' not found
$
$ nsxctl config set-site dummy --endpoint xxx -u xxx -p xxx
$ nsxctl show alb-cloud
Default-Cloud cloud-63d5653f-7a9e-4369-9430-6a3cf32aff88 CLOUD_VCENTER
$

@hichtakk hichtakk assigned hichtakk and mu853 and unassigned hichtakk Jul 15, 2022
@mu853
Copy link
Contributor Author

mu853 commented Aug 13, 2022

@hichtakk
Currently, logging into NSX-T or ALB is handled by NewCmdShow.
In that case, if the subcommand prefix is "alb-", you need to login ALB, but NewCmdShow cannot determine this.

So we have two options,
1: discard #28 feature (auto-completion of arguments) and login to NSX-T/ALB at each sub command.
2: make new sub command (nsxctl alb) and move the existing alb-xxxx sub commands to its sub commands.

example of use of option 2:

$ alias alb='nsxctl alb'
$ alb show vs

Do you have any other ideas?

mu853 pushed a commit to mu853/nsxctl that referenced this issue Dec 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants