particle-os/debian-forge-composer
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
debian-forge-composer/internal/image
History
Achilleas Koutsou c6bfb22f54 manifest: support specifying kickstart file location 
Add support for specifying where the kickstart file will be created:
either in the default location in the anaconda tree or at the root of
the ISO like we did so far in RHEL.

From the distro level, this is controlled by a boolean that when set to
true puts the kickstart file in the root of the ISO tree at /osbuild.ks
(the old behaviour) and if unset falls back to the default location
/usr/share/anaconda/interactive-defaults.ks.

Changed the name of the kickstart file for ostree back to osbuild.ks
Was ostree.ks for a while since a1bfcfe91c.

For Fedora we use the default and for RHEL we maintain the old behaviour
for now.
2022-11-28 17:20:49 +01:00
..
archive.go image: new ImageKind: archive 2022-11-28 17:20:49 +01:00
container.go image: introduce image kinds for Fedora 2022-07-22 16:04:07 +02:00
image.go image: add image kind abstraction 2022-07-22 16:04:07 +02:00
image_installer.go manifest: support specifying kickstart file location 2022-11-28 17:20:49 +01:00
live.go distro/rhel9: update gce images to new definitions 2022-11-28 17:20:49 +01:00
ostree_archive.go Separate ostree ref from parent spec in Pipelines and ImageKinds 2022-10-11 10:00:22 +02:00
ostree_container.go Separate ostree ref from parent spec in Pipelines and ImageKinds 2022-10-11 10:00:22 +02:00
ostree_installer.go manifest: support specifying kickstart file location 2022-11-28 17:20:49 +01:00
ostree_raw.go image: make read only sysroot optional for OSTreeRawImage 2022-10-11 10:00:22 +02:00