fix: Fix storage profiles list broken osFamily matching #252
Conversation
This file contains 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
Signed-off-by: Trevor Blanchard <blantrev@amazon.com>
epmog
approved these changes
Mar 27, 2024
lucaseck
approved these changes
Mar 27, 2024
Merged
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.
What was the problem/requirement? (What/Why)
Storage profiles no longer displayed in the config gui. The API had changed from using lower case "windows" to uppercase "WINDOWS" for the
osFamilyfield of the storage profiles.What was the solution? (How)
Convert to lower case when comparing against the current os to determine if a Storage Profile should be included in the list.
What is the impact of this change?
Storage Profile configuration works again.
How was this change tested?
Build and run locally.
Was this change documented?
no.
Is this a breaking change?
no.