Issue type
cli53 version (cli53 --version)
❯ ~/Downloads/cli53-mac-arm64 --version
cli53 version 0.8.22
OS / Platform
❯ uname -a
Darwin MD-0015 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct 9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000 arm64
Steps to reproduce
- Configure AWS CLI to use IAM Identity Center
[sso-session mysso]
sso_region = us-east-1
sso_start_url = https://mysso.awsapps.com/start
[default]
output = json
region = us-east-1
sso_account_id = 123456789012
sso_role_name = AdministratorAccess
sso_session = mysso
aws sso login
cli53 list
Expected behaviour
I would receive a list of hosted zones in my Route 53 account.
Actual behaviour
I received an empty list and echo $? returned "1"
❯ ~/Downloads/cli53-mac-arm64 list
❯ echo $?
1
Have you checked if the documentation has the information you require?
I have, yes, thanks!
Could you contribute a fix or help testing with this issue?
I don't need to. By cloning what is on main and running go build, the resultant binary executes the command properly. I did also clone the repository and ran a go get -u github.com/aws/aws-sdk-go before reverting my changes and trying a go build again. I'm hoping that didn't cloud the results of the operation, but it may have? Either way, an update of the AWS Go SDK wouldn't hurt, I don't think.
Issue type
cli53 version (cli53 --version)
OS / Platform
Steps to reproduce
aws sso logincli53 listExpected behaviour
I would receive a list of hosted zones in my Route 53 account.
Actual behaviour
I received an empty list and
echo $?returned "1"Have you checked if the documentation has the information you require?
I have, yes, thanks!
Could you contribute a fix or help testing with this issue?
I don't need to. By cloning what is on
mainand runninggo build, the resultant binary executes the command properly. I did also clone the repository and ran ago get -u github.com/aws/aws-sdk-gobefore reverting my changes and trying ago buildagain. I'm hoping that didn't cloud the results of the operation, but it may have? Either way, an update of the AWS Go SDK wouldn't hurt, I don't think.