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
Have you reproduced the bug with the latest dev version?
No
Version
main
Custom code
No
OS platform and distribution
No response
Describe the issue
We’ve encountered multiple cases where users have difficulty understanding that a subnet has been successfully created but cannot be listed. This happens because the subnet has not yet been activated (bootstrapped). Users find it confusing when the subnet doesn’t appear in the list command output.
Suggested Solution:
To improve clarity, I suggest including non-active subnets in the list command output, but with a flag (e.g., bootstrapped: true/false). This will help users see the status of subnets more clearly, making it easier to understand what’s happening within the system.
Repro steps
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
Issue type
Feature Request
Have you reproduced the bug with the latest dev version?
No
Version
main
Custom code
No
OS platform and distribution
No response
Describe the issue
We’ve encountered multiple cases where users have difficulty understanding that a subnet has been successfully created but cannot be listed. This happens because the subnet has not yet been activated (bootstrapped). Users find it confusing when the subnet doesn’t appear in the list command output.
Suggested Solution:
To improve clarity, I suggest including non-active subnets in the list command output, but with a flag (e.g., bootstrapped: true/false). This will help users see the status of subnets more clearly, making it easier to understand what’s happening within the system.
Repro steps
Relevant log output
No response
The text was updated successfully, but these errors were encountered: