Closed hh closed 7 years ago
@hh: I've had a lot of trouble with this flow in the past.
docker run -v $(pwd)/data:/data -ti generate/creds:azure To sign in, use a web browser to open the page https://aka.ms/devicelogin and enter the code *** to authenticate.
I am able to login and the container recognizes that I've done so and then outputs:
No subscriptions found for this account.
Of course I obviously have subscriptions on that Microsoft account and can see them in the portal that I just logged into. And this happens no matter how carefully I try this flow (even incognito in another browser).
In the past after many attempts the flow would complete properly. Sometimes. A lot of people have experienced these authentication problems if you search around. I'm also not a fan of having to run an opaque container (that presumably wraps the azure sdk/cli) for this.
I understand the reasoning here but I suggest to just provide the direct instructions for users to create ./data/azure.env
themselves.
The top of our azure readme has a tldr approach which is driven by a simple entrypoint container and seemed like a way to make it easy for folks.
I also put the manual instructions at the bottom. Both approaches use the official azuresdk/azure-cli-python container as a base.
How does the rest of the approach feel at the moment?
This initial PR should allow us to generate a kubernetes endpoint on Azure for use with cncf/demo and possible CI for other projects.