Hi @ofaakye! It looks like we got this sorted out via our Support Portal, but for anyone else following the problem here is rooted in a bug in Astronomer v0.16.1 of the CLI.
In Astro CLI v0.16.1, users get an error on
$ astro dev init and
$ astro version if they’re not authenticated to Astronomer (though they shouldn’t need to be).
While our team works on a patch release, however, you do have to authenticate to Astronomer in order to run most (if not all)
astro commands. To do so, run the following depending on what product of Astronomer you’re running:
$ astro auth login gcp0001.us-east4.astronomer.io
$ astro auth login BASEDOMAIN
BASEDOMAIN with the basedomain of your cluster/platform (e.g. astronomer.mycompany.com)
From there, you’ll be prompted to follow our authentication flow either via Google/GitHub OAuth or local username/password and should be able to run any command of your choosing.
Authenticate to Astronomer CLI via OAuth
If you’re authenticating via OAuth, follow the steps below.
$ astro auth login..., leave ‘username’ blank and press
- You will receive a link in your command line to a URL that will redirect you to the Astronomer UI to retrieve an authentication token (something like https://app.gcp0001.us-east4.astronomer.io/token)
- Navigate to the URL via your browser and copy the token (if you’re redirected to the Astronomer UI login screen, login with your account and then you will be redirected to the token)
- Now, paste that token in your command line against
oAuth Token: and press
- You will be successfully Authenticated
Hope this helps! Thanks again for raising this issue, @ofaakye.