Fix drive section #1387
Merged
Fix drive section #1387
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
|
✅ Autosubmission job #10562222369 successfully finished |
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.
Problem
Agama calculates an AutoYaST proposal from a given JSON config file. Such a config file is a direct conversion from XML to JSON. This implies that some symbol attributes (e.g., type from drive section) are converted to string (JSON does not support symbols).
The AutoYaST proposal code works fine with strings instead of symbols, for example for the fileystem type, encryption method, etc. Except for the
typeattribute, which must be a symbol.Solution
Ensure the type attribute is a symbol when importing a hash.
Required by agama-project/agama#1471.