fix: check for duplicated chip numbers in relevant services
Description
How to test
Everything should be set up on this resource. Meaning all services are assigned and relevant attributes are created and set. There are users with duplicated chipNumbers on the resource so all relevant services should fail.
Author's checklist
-
I have followed the contribution guidelines -
This MR has been tested or does not change functionality -
I have added relevant merge request dependencies (if this MR has any) -
I have added the correct labels -
I have assigned reviewers (if any are relevant) -
I have edited the documentation (if the changes require it) or I have noted the need for the change if I do not have access to the documentation -
I have marked all introduced BREAKING CHANGES or necessary DEPLOYMENT NOTES in the commit message(s)
Reviewer's checklist
-
This MR has been tested or does not change functionality -
This MR has correct commit message format
Other information
According to the task description the check should be also implemented for the tinia
service, but the check seems to be already there.
Related issues
Closes STR-1307
Edited by Rastislav Kruták