Fix args order in strings.Contains in es-rollover #3324
Merged
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.
Closes #3319
If we do
strings.Contains("resource_already_exists_exception", errorMap["type"].(string))
,we're basically doing
"resource_already_exists_exception" == errorMap["type"].(string)
.I would assume that we intended to test whether
errorMap["type"]
contains"resource_already_exists_exception"
as a substring, so the reversestrings.Contains
orderis more applicable here.
Signed-off-by: Pavol Loffay [email protected]
Which problem is this PR solving?
Short description of the changes