From: Emanuele Giuseppe Esposito on
gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2917#note_1760...
@prudo1 what about the SBAT? we might want to add that too. But then that may
be shared between all addons I guess
@berrange what do you think of the filesystem based structure described above?
I think it might make sense.
We would have a root folder redhat/addons and inside an arch hierarchy (or
anything you want).
For example
```
ls redhat/addons
x86_64
output
sbat
...
ls redhat/addons/sbat
sbat.conf
cat redhat/addons/sbat/sbat.conf
sbat,1,......
uki.addon,1,....
ls redhat/addons/x86_64
fips.addon
kdump
...
cat redhat/addons/x86_64/fips
# fips cmdline
fips=1
ls redhat/addons/x86_64/kdump
addon-something.addon
cat redhat/addons/x86_64/kdump/addon-something
# this addon is useful for ???
crashkernel=????
```
And when the build is triggered, we get two addons in redhat/addons/output:
```
fips-x86_64.addon.efi (cmdline="fips=1" sbat="cat sbat.conf")
addon-something-kdump-x86_64.addon.efi (cmdline="crashkernel=???"
sbat="cat
sbat.conf")
```
What do you think?