-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI helpers for user to select resource group and subscription #265
Comments
I pinned all Azure issues to v0.26, we will either address them or close them out. I'd mostly like to ensure we haven't broken any Azure functionality and document any limitations, like the Azure API and CLI holding their source of truth outside of Git, or any resources you cannot resume/suspend or reconcile from within the UI, etc. I don't know what issues there might still be. I just closed a bunch of older issues that definitely haven't been followed up. That doesn't mean the things are/aren't still broken, but those reports are obsolete at the very least. |
The official instructions from Azure as far as I can tell guide the user through the
az aks
CLI to a terminal workflow that emits some blobs of JSON, and they are expected to find the resource group ID and subscription ID in the output without any help.This is extremely user hostile, why don't we do all of this for them, and present the possible selections for them in the UI, in a list? There's no sense sending them back to the terminal twice to fetch some GUID, if there's a process for listing them we should invoke that process and parse the output, then present the choices in a list (the record name, not the GUID – or the record name presented alongside of the GUID, if you prefer) and let the user pick the right one.
An open question is, how to present this information more effectively when there are thousands of entries in the list. (Can we expect that to happen for some substantial fraction of users? I think so, but I'm stopping myself short of suggesting this picker should be an autocomplete text entry widget. If it turns out that it's easier to do that UX though we should absolutely do it.)
The text was updated successfully, but these errors were encountered: