Hi,
In the current behavior of ign-converter, we rely on a fsMap in order to mitigate a change between Ignition 2.x and 3.x:
map[string]string{"var": "/var"}
without this map or the correct values in it, we fail the translation in case we hit a filesystem with no associated path:
|
for _, fs := range cfg.Storage.Filesystems { |
|
if _, ok := fsMap[fs.Name]; !ok { |
|
return util.NoFilesystemError(fs.Name) |
|
} |
|
} |
Did we already consider in the past generating a random path associated to this filesystem name in order to circumvent this requirement ?
This is a proof-of-concept using randomized name: main...tormath1:tormath1/generate-path-upstream and the logic has been tested in Flatcar CI.
Thanks :)
Hi,
In the current behavior of
ign-converter, we rely on afsMapin order to mitigate a change between Ignition 2.x and 3.x:without this map or the correct values in it, we fail the translation in case we hit a filesystem with no associated path:
ign-converter/translate/v24tov31/v24tov31.go
Lines 50 to 54 in 984c88c
Did we already consider in the past generating a random path associated to this filesystem name in order to circumvent this requirement ?
This is a proof-of-concept using randomized name: main...tormath1:tormath1/generate-path-upstream and the logic has been tested in Flatcar CI.
Thanks :)