-
Notifications
You must be signed in to change notification settings - Fork 190
mantle: support Butane in platform/conf; use that rather than shelling out or hardcoding Ignition
#2246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
mantle: support Butane in platform/conf; use that rather than shelling out or hardcoding Ignition
#2246
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
f100f44
mantle/go.sum: go mod tidy
bgilbert e28a2ee
mantle/go.mod: vendor Butane
bgilbert f8994a0
mantle/platform/conf: make the config an argument to renderIgnition
bgilbert a80cb4a
mantle/platform/conf: support Butane configs
bgilbert c37a1a4
mantle/kola/tests: update RAID tests to use Butane
bgilbert e7856c6
mantle/kola/tests: update some disabled tests to pretend to use Butane
bgilbert f7c65f5
mantle/kola: accept .bu suffix for Butane config in external test
bgilbert e5b3cbb
mantle/kola: pass conf.UserData to registerExternalTest()
bgilbert 652b6ef
mantle/kola: don't shell out to render Butane configs for ext tests
bgilbert c4f0009
mantle/kola/qemuexec: don't shell out to render Butane configs
bgilbert File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's less exact but technically we could always group the Ignition & Butane/FCCT sections together and use
conf.Unknown's detection logic no? Could maybe even loosen it toconfig*as the qualifier for a config object if we go that route.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I thought about that. Since we already have separate command-line options to distinguish the config types, I'm inclined to keep using those, rather than combining them and expecting the code to guess.