Ambassador: edgectl fail to login

Created on 1 Jun 2020 · 7Comments · Source: datawire/ambassador

Describe the bug
$ edgectl login --namespace=ambassador myapi.com
panic: CmdUsage is not empty: map[upgrade:0xc000668c80]

goroutine 1 [running]:
github.com/datawire/ambassador/internal/pkg/edgectl.NewCmdUsage(0xc0006fd180, 0xc000695f00, 0x2, 0x2, 0xc000695f20)
github.com/datawire/ambassador@/internal/pkg/edgectl/cmd_usage.go:46 +0x91c
main.main()
github.com/datawire/ambassador@/cmd/edgectl/main.go:54 +0x143

To Reproduce
Steps to reproduce the behavior:

Go to Command Prompt
$ edgectl login --namespace=ambassador myapi.com
See error

Expected behavior
Login to api gateway

bug

Source

katlimruiz

👍2

All 7 comments

how can I get ambassador version without entering to the console? kubectl describe?

katlimruiz on 1 Jun 2020

yes, if you kubectl describe ambassador -n ambassador, there should be a field that says image. The version number after that is the version number. What does edgectl version say?

cakuros on 4 Jun 2020

I'm having the same issue with edgectl on Windows. It seems like no matter what command I run I always get the CmdUsage is not empty error. I put edgectl.exe into 'C:/edgectl/' and added 'C:/edgectl/' to my PATH environment variable. I am running the commands from Git Bash, but the same error happens in Windows Command Prompt too. This is what I get running edgectl version:

edgectl version
panic: CmdUsage is not empty: map[upgrade:0xc000588500]

goroutine 1 [running]:
github.com/datawire/ambassador/internal/pkg/edgectl.NewCmdUsage(0xc0001f1b80, 0xc000737f00, 0x2, 0x2, 0xc000737f20)
        github.com/datawire/ambassador@/internal/pkg/edgectl/cmd_usage.go:46 +0x91c
main.main()
        github.com/datawire/ambassador@/cmd/edgectl/main.go:54 +0x143

Seems like the latest release of edgectl on Windows is broken?