From 9511c760633ec922ea99da2540073d15918be343 Mon Sep 17 00:00:00 2001
From: Achilleas Koutsou <achilleas@koutsou.net>
Date: Tue, 29 Nov 2022 19:46:08 +0100
Subject: [PATCH] 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.
---
 internal/manifest/coreos_installer.go | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/internal/manifest/coreos_installer.go b/internal/manifest/coreos_installer.go
index fd3e42f38..cf913be3a 100644
--- a/internal/manifest/coreos_installer.go
+++ b/internal/manifest/coreos_installer.go
@@ -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.