Fix AWS AppMesh issue when providing multiple backends #831
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.
Signed-off-by: Joao Carreira jddcarreira@gmail.com
When adding multiple backend (by arn or by virtual service name), while using AWS App Mesh as a provided, Flagger was returning the following error:
This was caused by a wrong usage of
range
, since in a range when targeting the pointer of an element it seems to return the object of the slice and not the object of the element in the slice.https://golang.org/doc/effective_go#slices
Here's a representation of what was happening:
In this MR we make use of the index to access the element of the slice, representing each backend.