-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Rust-based Azure CLI version #32612
Copy link
Copy link
Open
Labels
Azure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.performancequestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Metadata
Metadata
Assignees
Labels
Azure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.performancequestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Hi azure-cli team!
In our organization (Ahold Delhaize) we use the Azure CLI quite a lot, however the performance in both CI and interactive scenario's has proven difficult. In our organization we therefore have a complete rewrite of the Azure CLI in Rust (called
raz), with a codegen that automatically generates extension modules based on the Azure OpenAPI / Swagger specs.Extensions are dynamically loaded in when requested by WebAssembly, and support all operations that the specs define.
Binary size of the CLI is around 3MiB, and extensions (like compute) are around ~50KiB, so this makes for a very snappy experience no matter how big the module is / the operation.
We would like to discuss open-sourcing this, and maybe partnering up with you guys to see if this is not the logical avenue where the Azure CLI should go?