Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
[UI] Edit modal remains fully interactive during ongoing disk resize operation
Description
Steps to Reproduce:
Initiate disk resize.
While the cluster is still resizing, open Edit Resources or any other option on the cluster.
Actual Outcome:
All fields remain clickable and editable, including disk size.
Expected Outcome:
Modal should either:
Be disabled entirely, or
During disk resizing, the Edit modal should allow changes only to fields that are safe and independent of the resizing operation. This includes all operations like monitoring, external access etc.
When Disk resize in progress. Disk size cannot be changed until the current operation completes. This ensures a smooth experience while still allowing parallel updates that don’t interfere with volume expansion.
Example:
If a disk resize is in progress, you can still enable monitoring for the DB cluster. However, the cluster status will not reflect the typical Initializing state that usually appears when monitoring is enabled. If we choose to keep these options available on the UI during resizing, we need to ensure that they function correctly and do not conflict with the ongoing operation.
Steps to Reproduce:
Initiate disk resize.
While the cluster is still resizing, open Edit Resources or any other option on the cluster.
Actual Outcome:
All fields remain clickable and editable, including disk size.
Expected Outcome:
Modal should either:
Be disabled entirely, or
During disk resizing, the Edit modal should allow changes only to fields that are safe and independent of the resizing operation. This includes all operations like monitoring, external access etc.
When Disk resize in progress. Disk size cannot be changed until the current operation completes. This ensures a smooth experience while still allowing parallel updates that don’t interfere with volume expansion.
Example:
If a disk resize is in progress, you can still enable monitoring for the DB cluster. However, the cluster status will not reflect the typical Initializing state that usually appears when monitoring is enabled. If we choose to keep these options available on the UI during resizing, we need to ensure that they function correctly and do not conflict with the ongoing operation.