-
Notifications
You must be signed in to change notification settings - Fork 4
list zones for vms for anyzone autoreserved nodes #228
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
base: main
Are you sure you want to change the base?
Conversation
Greptile OverviewGreptile SummaryThis PR enhances the VM display for auto-reserved nodes by showing zone information at the VM level when the node doesn't have a specific zone assignment.
This change improves visibility into where VMs are running for multi-zone auto-reserved deployments. Confidence Score: 5/5
Important Files ChangedFile Analysis
Sequence DiagramsequenceDiagram
participant User
participant CLI
participant API
participant VMTable
User->>CLI: sf nodes ls --verbose
CLI->>API: client.nodes.list()
API-->>CLI: nodes with vms data
Note over API,CLI: VMs now include optional zone field
CLI->>VMTable: render(<NodesVerboseDisplay>)
VMTable->>VMTable: Check if node.zone exists
alt node.zone is null (auto-reserved any-zone)
VMTable->>VMTable: showZoneColumn = true
VMTable->>User: Display VM table with Zone column
Note over VMTable,User: Shows individual VM zones
else node.zone exists (reserved)
VMTable->>VMTable: showZoneColumn = false
VMTable->>User: Display VM table without Zone column
Note over VMTable,User: Zone displayed at node level only
end
|
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.
2 files reviewed, no comments

No description provided.