-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider supporting .d directory for base config fragments #1101
Consider supporting .d directory for base config fragments #1101
Comments
While we're here, we might also want to support an additional .d directory for each platform ID. |
This looks like a useful generalization of the |
I was thinking this would only affect base configs for now. For user configs I think there's value in maintaining the current model, with a single well-defined root config that explicitly merges sub-configs. For base configs I think that's less important, since the "config built up from fragments" model is pretty well-understood in distro maintenance. |
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which requires the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which requires the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which requires the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which requires the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which allows the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which allows the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which allows the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which allows the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which allows the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which allows the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which allows the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which allows the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change was inspired by coreos/fedora-coreos-config#626, which allows the two distros to carry different base.ign files with common elements. Also, this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change allows the two distrosi (i.e. FCOS and RHCOS) to carry different base.ign files with common elements. Also,this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change allows the two distrosi (i.e. FCOS and RHCOS) to carry different base.ign files with common elements. Also,this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change allows the two distrosi (i.e. FCOS and RHCOS) to carry different base.ign files with common elements. Also,this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change allows the two distrosi (i.e. FCOS and RHCOS) to carry different base.ign files with common elements. Also,this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change allows the two distrosi (i.e. FCOS and RHCOS) to carry different base.ign files with common elements. Also,this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change allows the two distrosi (i.e. FCOS and RHCOS) to carry different base.ign files with common elements. Also,this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change allows the two distrosi (i.e. FCOS and RHCOS) to carry different base.ign files with common elements. Also,this will support an additional .d directory for each platform ID.
Fixes coreos#1101 This change allows the two distrosi (i.e. FCOS and RHCOS) to carry different base.ign files with common elements. Also,this will support an additional .d directory for each platform ID.
We're starting to have divergence between the FCOS and RHCOS base configs (coreos/fedora-coreos-config#626), which requires the two distros to carry different
base.ign
files with common elements. Consider supporting a.d
-style base config directory, where Ignition walks the directory and merges every config fragment in it.The text was updated successfully, but these errors were encountered: