-
Notifications
You must be signed in to change notification settings - Fork 115
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
Add new command command-change tree-export
to export command tree
#448
Conversation
Hi @ReaNAiveD, |
if not module_loader: | ||
continue | ||
module_loader = module_loader[0] | ||
module_path = module_loader.__class__.__module__ |
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.
extension module name: azext_spring, azext_amcs etc
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.
Use _get_command_source
to retrieve the extension name.
if not subtree.get(part): | ||
subtree[part] = {} | ||
subtree = subtree[part] | ||
subtree[parts[-1]] = module_name |
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.
It would be more clear if expected command tree structure is provided or through test.
Description
I propose to introduce a new command or add new parameters to facilitate the exportation of the command tree.
Once exported, this command tree could be uploaded to our storage account. This would enable the CLI Validation Tool to dynamically load command metadata, significantly improving its functionality and efficiency.