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
feat(version): warn when vendored charts drift from the talm binary
talm renders from the project's vendored charts/talm/, never the
binary's built-in charts, so upgrading the binary leaves the library
frozen at the version that last ran init — drift that was previously
invisible. On every config-loading command a release build now compares
the two and, by default, prints a non-fatal warning to stderr pointing
at `talm init --update`; stdout and the exit code are unchanged.
A project (strictCharts: true in Chart.yaml) or an operator
(--strict-charts) can promote the warning to a hard error raised before
the command body runs. The check is a no-op for dev/source builds, whose
embedded charts are a moving target the developer controls, and a
best-effort I/O failure never blocks a command.
Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
cmd.PersistentFlags().Bool("version", false, "Print the version number of the application")
132
+
cmd.PersistentFlags().BoolVar(&strictChartsFlag, "strict-charts", false, "fail if the project's vendored charts/talm/ differs from the talm binary's built-in copy (run `talm init --update` to re-sync)")
124
133
125
134
// Shell completion for root persistent flags. --nodes /
126
135
// --endpoints draw from the in-scope talosconfig contexts.
0 commit comments