Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
New configuration introduced by IGNITE-5466 lacks a way to clone cluster configuration child entities (caches, igfss and domain models).
What to do:
Implement cluster config entity cloning mechanism. It might be a single (or multiple) items table context action, which creates new entities under the hood using a default unique name generator function, sends one or multiple requests to the backend and shows an error notification if something goes wrong.
Potential issues:
1. Nested reference IDs and what to do with them.
2. If user decides to clone current edited item, can unsaved changes trigger any unwanted behavior?
3. One vs multiple items to clone at the same time.
Additional ideas:
1. Clone the item specified amount of times. Useful when user needs 10 caches with similar configuration.
Attachments
Issue Links
- is blocked by
-
IGNITE-5466 Web Console: New Configuration Screen
- Closed