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
#918 has implemented support for changing IDs while keeping entities' names between deck syncs for Service, Route, and Consumer entities.
The goal of this issue is to implement similar behavior for every entity that still can be affected by the lack of this capability due to unique constraints enforced on some property of the entity other than its ID.
Affected entities:
Upstream (a unique constraint on name)
... TBD
Proposed solution
Similarly to #918, implement DuplicatesDeleter interface in every entity's differ and generate Delete events once a duplicate is detected. Make sure that any implicit cascade deletes are handled in the entity's *PostAction.
Acceptance criteria
It's possible to run deck syncs twice, changing only the ID properties of all entities between each run
The text was updated successfully, but these errors were encountered:
Description
#918 has implemented support for changing IDs while keeping entities' names between deck syncs for Service, Route, and Consumer entities.
The goal of this issue is to implement similar behavior for every entity that still can be affected by the lack of this capability due to unique constraints enforced on some property of the entity other than its ID.
Affected entities:
name
)Proposed solution
Similarly to #918, implement
DuplicatesDeleter
interface in every entity's differ and generate Delete events once a duplicate is detected. Make sure that any implicit cascade deletes are handled in the entity's*PostAction
.Acceptance criteria
The text was updated successfully, but these errors were encountered: