Fix incompatible changes introduced with diego release 2.109.0#111
Closed
ivo9999 wants to merge 2 commits intocloudfoundry:mainfrom
Closed
Fix incompatible changes introduced with diego release 2.109.0#111ivo9999 wants to merge 2 commits intocloudfoundry:mainfrom
ivo9999 wants to merge 2 commits intocloudfoundry:mainfrom
Conversation
…uced-with-Diego-release-2.109.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The PR makes sure the FSes are always used in a consistent way. The map was removed in favour of an array. The FSes should be stored in ascending order, ie. [ cflinuxfs3, cflinuxfs4 ]
The github issue: cloudfoundry/diego-release#983
Backward Compatibility
Breaking Change? No
No breaking changes, just making sure the fses are used in a consistent way