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
Would it be possible to enable autocompletion for custom CLI parameters passed into atmos.yaml?
This would allow for adding a complete section to atmos.yaml so that custom commands can be autocompleted. An example of this would be by adding the following to atmos.yaml:
complete:
enable: truefuzzyMatching: true
Where we could define completeFunctions to dynamically fetch data for autocompletion and attach functions to arguments/flags
# Functions to complete oncompleteFunctions:
- name: componentsexec:
- atmos list components# Attach to function
- name: describedescription: Execute 'describe' commands# subcommandscommands:
- name: k8s-upgradedescription: "Describe the steps on how to upgrade an EKS cluster to the next Kubernetes version. Usage: atmos describe k8s-upgrade <eks_component> -s <stack>"arguments:
- name: componentdescription: Name of the EKS componentcomplete:
- components
Maybe this could be achieved by doing something similar to:
Describe the Feature
Would it be possible to enable autocompletion for custom CLI parameters passed into
atmos.yaml
?This would allow for adding a
complete
section toatmos.yaml
so that custom commands can be autocompleted. An example of this would be by adding the following toatmos.yaml
:Where we could define
completeFunctions
to dynamically fetch data for autocompletion and attach functions to arguments/flagsMaybe this could be achieved by doing something similar to:
Expected Behavior
An example command would be:
where the ... would autocomplete
Use Case
This feature is just for ease of use and quality of life improvements.
Describe Ideal Solution
Whichever way is the easiest and most painless way to implement.
Alternatives Considered
Not sure if it is easier to incorporate into a custom
atmos.yaml
file.Additional Context
No response
The text was updated successfully, but these errors were encountered: