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
fix(applycheck): correct YAML field names against real Talos schema
Walker was using YAML keys I guessed from Talos doc strings, not
verified against the actual v1alpha1 struct tags. Two of them were
wrong, silently turning the walker into a no-op for the affected
document class:
- BridgeConfig: tag is 'links' (BridgeLinks), I had 'ports'.
- VLANConfig parent: tag is 'parent' (ParentLinkConfig), I had
'link'.
Real-Talos consequence: BridgeConfig slaves were never validated;
VLANConfig parent was never validated. The unit tests passed only
because the fixture YAML mirrored my (wrong) guess.
Also adds HCloudVIPConfig (hcloud_vip.go LinkName 'yaml:link') to
the dispatch table; it has the same Layer2VIPConfig shape and
shares the handler.
New test TestWalkRefs_v1_12_RealTalosYAMLKeys pins each tag against
its struct definition so a future tag rename in machinery (or
another walker oversight) surfaces immediately.
Verified on the dev17 OCI cluster: BridgeConfig with a typoed
'missing-port' in .links[] now blocks; VLANConfig with a typoed
'ghost-parent' in .parent now blocks. Pre-fix both went silent.
Refs: #172
Signed-off-by: Aleksei Sviridkin <f@lex.la>
0 commit comments