@mihaidma, this PR ignores conflicts on insert policy (note: if updates are performed on policy instances, we will throw the conflict error)
this PR also changed validation so that ids in team/user arrays can be empty for consistency to be like policies as per slack channel discussion, if there are entries it also enforces the id validation.
I'm not sure it makes sense to allow empty on PUT, we can add to all if necessary by putting min for each payload array...
Coverage decreased (-0.09%) to 93.141% when pulling f594a50723fe41054c2b7de8ccaeb429e90e699b on no-conflict-on-insert-policy into f7538655faf92e4116bc218e38e1fb142676c8cf on master.
@mihaidma, this PR ignores conflicts on insert policy (note: if updates are performed on policy instances, we will throw the conflict error)
this PR also changed validation so that ids in team/user arrays can be empty for consistency to be like policies as per slack channel discussion, if there are entries it also enforces the id validation.
I'm not sure it makes sense to allow empty on PUT, we can add to all if necessary by putting min for each payload array...