Parity between BIOS and BMCSettings Spec

[nagadeesh-nagaraja]

Why it make sense to have parity between these two spec

1. The BMCSettings also needs possibility to set group of settings in certain order, similar to BIOSSettings
2. The BIOSSettings will also help having variables in case its used in future
3. The required between BIOS and BMC Settings are similar

Hence, having similar Spec help in maintenance and future development

Further, there is a requirement to support apply BMC/BIOS Settings to the Version the BMC/Server come with (which can be unknown). Providing ability for SET object to patch the Version spec at the time of creation helps handling this requirement.

providing ability to support multiple Settings obj ref to the BMC/Server help handing setting segregation which are dependent on version.

branched from #814

[coderabbitai]

🔗 Related PRs

#581 - Transition Server to Maintenance in case of pending BIOS settings exist [merged]
#651 - Update BIOSSettings docs [merged]
#723 - Simplify BMCSettings reconciler and fix bugs [merged]
#804 - Change BMC dynamic settings variables definition [merged]
#902 - BMC Settings Spec to support display names for enum typed settings attributes for Dell [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[nagadeesh-nagaraja]

baseline-settings-changes.md