[ANSIENG-4314] | Adding check sub property role for testing comma seperated list of values #1869
+73
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In a couple of test cases we had a check to confirm the value of
sasl.enabled.mechanisms
is set toGSSAPI,PLAIN
but it could also have been set toPLAIN,GSSAPI
. so instead of doing a string matching of values we can parse the value and split by comma and make a list. Then compare items of list to ensure all the mechanisms which should be present are actually present.This will help remove flakiness as at times this property would be set to
GSSAPI,PLAIN
and at other times it would bePLAIN,GSSAPI
both of which are same from cp point of view.Fixes # (issue)
Type of change
How Has This Been Tested?
Semaphore link - [add here]
Checklist: