fix: attach volume key choice #184
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.
Currently, when attaching a volume, the sdk attach it to the ID that is the len of the volume list. Unfortunately, if the list is
0, 1, 2and the volume1is removed, the list becomes0, 2. This leads to a newly attached volumes to be attached to the ID2, thus overriding the already existing volume. This fix this issue by looping over all the keys, and attaching to a non existent key.Signed-off-by: Patrik Cyvoct [email protected]