in_systemd: pass storage conf to storage_create to support named storage#140
Merged
Merged
Conversation
Previously, `storage_create` was called without the `conf` argument, which prevented it from properly parsing named storage sections . This commit extracts the storage configuration and explicitly passes it to `storage_create` along with `default_type`. This ensures that named storage settings are correctly applied and accurately reflected in the storage paths.
kenhys
approved these changes
Jun 15, 2026
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
2 participants
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.
Previously,
storage_createwas called without theconfargument, which prevented it from properly parsing named storage sections .This commit extracts the storage configuration and explicitly passes it to
storage_createalong withdefault_type.This ensures that named storage settings are correctly applied and accurately reflected in the storage paths.
Fix #109