Change Service
Uniqueness Constraint
#3845
Labels
impact: breaking change
This change or feature will remove or replace existing functionality; needs to be an X.0.0 release
type: housekeeping
Changes to the application which do not directly impact the end user
Milestone
Carved out of #2908
Proposed Changes
Unique together:
(device, name)
and(vm, name)
with natural key(name, device, vm)
; for duplication use other fields to help add to name uniquenessThe text was updated successfully, but these errors were encountered: