I have a config srgb and srlb configs which take preconfigured label blocks (consists of lower bound and upper bound). For these, we have a validation checking if the configured label block is already been used for different srgb or srlb, if yes it throws an error.
ABove validation works fine if we configure different srgbs or srlbs in seperate commits. But if a user configues SRGB1 and SRLB1 with same label block block1 in same commit, validation does not work.
Example config
label block block1
lower-bound x1
uppder-bound x2
end
srgb srgb1
id srgb1
label-blocks [block1]
srgb srlb1
id srlb1
label-block [block1]
above sample config does not go throw with seperate commits due to tailf validation. But it validation does not kick in if the both config is committed in same commit.
Is there a way to block this happening in single commit through validation?