manifest: use options from fdo package instead of blueprint
Use the internal representation of the FDO options in on the CoreOSInstaller pipeline instead of the blueprint.
This commit is contained in:
parent
836dddbb33
commit
9511c76063
1 changed files with 2 additions and 2 deletions
|
|
@ -3,7 +3,7 @@ package manifest
|
|||
import (
|
||||
"fmt"
|
||||
|
||||
"github.com/osbuild/osbuild-composer/internal/blueprint"
|
||||
"github.com/osbuild/osbuild-composer/internal/fdo"
|
||||
"github.com/osbuild/osbuild-composer/internal/osbuild"
|
||||
"github.com/osbuild/osbuild-composer/internal/platform"
|
||||
"github.com/osbuild/osbuild-composer/internal/rpmmd"
|
||||
|
|
@ -33,7 +33,7 @@ type CoreOSInstaller struct {
|
|||
// the naming of network devices on the target system.
|
||||
Biosdevname bool
|
||||
|
||||
FDO *blueprint.FDOCustomization
|
||||
FDO *fdo.Options
|
||||
}
|
||||
|
||||
// NewCoreOSInstaller creates an CoreOS installer pipeline object.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue