You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We did discuss it in the past — actually I think I may have proposed it — but ultimately we decided against it. Unfortunately I don't remember why, I don't think we recorded it anywhere, and the lead developer at the time is no longer involved in the project.
@bgilbert ok I see - good to know that you already considered it.
If well documented, it could be a default behavior:
user provides a fsMap, it behaves as currently
user does not provide a fsMap, it generates random path
If we really don't want to be a default behavior, we could even consider to supply a particular value (like we already do with map[string]string{"root": "/"]) - like map[string]string{"rand": ""}.
Hi,
In the current behavior of
ign-converter
, we rely on afsMap
in 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 :)
The text was updated successfully, but these errors were encountered: