In the future, the main authentication method for DNX will be AWS SSO. So we need to start preparing the CLI to authenticate using this SSO.
Describe the solution you'd like
The first solutions that came in my mind were to use a container with AWS CLI 2 (have support to auth with their SSO) and call:
aws configure sso
The main problem with this solution is that during the authentication process the AWS CLI will open the user default browser and because we are running inside docker this part could generate errors. Only testing to see...
Describe alternatives you've considered
Another alternative is to reimplement all AWS API calls inside the DNX CLI. This will require more work but we can guarantee that the default user browser will be open properly.
Is your proposal related to a problem?
In the future, the main authentication method for DNX will be AWS SSO. So we need to start preparing the CLI to authenticate using this SSO.
Describe the solution you'd like
The first solutions that came in my mind were to use a container with AWS CLI 2 (have support to auth with their SSO) and call:
The main problem with this solution is that during the authentication process the AWS CLI will open the user default browser and because we are running inside docker this part could generate errors. Only testing to see...
Describe alternatives you've considered
Another alternative is to reimplement all AWS API calls inside the DNX CLI. This will require more work but we can guarantee that the default user browser will be open properly.