Draft: fix: Status message for bulk change tier when error occurs
Type of change
-
Bug Fix -
Feature -
Pipeline -
Test -
Documentation
Does this introduce a change in the core logic?
-
No -
Yes
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Anthos -
Azure -
GCP -
IBM
conventional commits spec?
Does this follow-
No -
Yes
Have you set the target Milestone?
-
No -
Yes
Have you set the no-detached-pipeline label?
-
No -
Yes
Updates description?
- Introduced a flag to keep track of the error in any of the pages, and update status message at the end based on the error Flag value avoiding overwriting of the status message.
- Dataset lock errors are now captured and returned.
Edited by Kajal Sawale