-
Notifications
You must be signed in to change notification settings - Fork 933
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
CLI: Improvements to lxc config
and lxc profile
shell completions
#14542
CLI: Improvements to lxc config
and lxc profile
shell completions
#14542
Conversation
lxc config
and lxc profile
completionslxc config
and lxc profile
shell completions
adab00b
to
f212bc3
Compare
This commit reworks the `cmpInstanceKeys` function to use the metadata API rather than `instancetype`. Signed-off-by: Kadin Sayani <[email protected]>
63e2d12
to
bde5185
Compare
Signed-off-by: Kadin Sayani <[email protected]>
…cmpInstances` function Signed-off-by: Kadin Sayani <[email protected]>
This commit adds a completion function for completing config keys which are currently set. Signed-off-by: Kadin Sayani <[email protected]>
bde5185
to
e9d18f2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@kadinsayani @simondeziel has any consideration been thought about wrt to caching the metdata api response for a particular remote so it doesnt have to keep re-requesting it (perhaps tied to the version number returned by the remote's /1.0 api)? |
I'll include this with #14543 :) |
That's an interesting idea, thanks for suggesting! I'd probably tie it to the |
This PR includes updates to
lxc/completion.go
, improving the shell completion functionality for instance configuration keys.Summary of changes:
cmpInstanceKeys
andcmpInstanceAllKeys
functions to use the metadata API (resolves Missing instance config suggestions from tab completion #14537);cmpInstanceSetKeys
function for improvedlxc config unset
completions.