Conversation
it mainly brings back Vagrant which was failing with Ignition 2.14.0 even if no Ignition is provided. Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
krnowak
left a comment
There was a problem hiding this comment.
I'm wondering if this shouldn't be fixed by using noop.FetchConfig for the unregistered platforms, but I suppose this is outside the scope of this PR.
What do you mean by that? |
Basically if somewhere in Ignition code there should be a snippet like (instead of trying to list all the old platforms): if config, ok := configs.getConfigForPlatformOrSomething(platformName); ok {
config.fetch(…)
} else {
# platform not registered, assume noop.FetchConfig will be enough for its needs
noop.FetchConfig(…)
}But wrt. Ignition, I'm an uninformed keyboard puncher here, so I might be spouting nonsense. :) |
|
@krnowak I'll go ahead for now - this is something we can suggest and track directly into the upstream |
|
picked to:
As it concerns Ignition, I think it's safer to test in Beta before picking it to stable. |
Sure, sounds good. |
it mainly brings back Vagrant which was failing with Ignition 2.14.0 even if no Ignition is provided.
Signed-off-by: Mathieu Tortuyaux mtortuyaux@microsoft.com
changelog/directory (user-facing change, bug fix, security fix, update)/bootand/usrsize, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.NOTE: It's ok to me to backport on all channels: the added platforms were not just working before.
Related to: flatcar/Flatcar#916