You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, a lot of rad cli commands take arguments like resource group, resource types etc.
We also have to specify a fully qualified resource type(ex: applications.core/container) for our rad resource commands because of introduction of UDT. This requires a good amount of typing.
Some tools, like kubernetes can autocomplete names for us, for instance if we type kubectl get pods -n mynamespace, we can expect pod names to be auto completed although they are "dynamic" list.
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
Today, a lot of rad cli commands take arguments like resource group, resource types etc.
We also have to specify a fully qualified resource type(ex: applications.core/container) for our rad resource commands because of introduction of UDT. This requires a good amount of typing.
Some tools, like kubernetes can autocomplete names for us, for instance if we type kubectl get pods -n mynamespace, we can expect pod names to be auto completed although they are "dynamic" list.
https://chromium.googlesource.com/external/github.com/spf13/cobra/+/94a87a7b83bda98e918cf7a4793f41372a5e4139/bash_completions.md captures a potential approach for cobra commands.
We should investigate and add this feature for UX enhancement.
AB#14660
The text was updated successfully, but these errors were encountered: