Skip to content

feat(template): Generate NOTES.txt for every operator chart - #646

Merged
lfrancke merged 1 commit into
mainfrom
push-sxyorkmlyklx
Sep 8, 2026
Merged

feat(template): Generate NOTES.txt for every operator chart#646
lfrancke merged 1 commit into
mainfrom
push-sxyorkmlyklx

Conversation

@lfrancke

@lfrancke lfrancke commented Sep 2, 2026

Copy link
Copy Markdown
Member

I started rolling out NOTES.txt for Helm by hand in all operators because I thought it'd be too complicated to special-case them. Turns out we have all the necessary plumbing already in operator-templating.

The special handling is needed due to commons, listener and secret operator not having a "product".

This installs the Stackable operator for Secret Operator only. <-- Wrong
Instead it does now emit This installs the Stackable Secret Operator only.

helm install currently prints nothing. This adds the NOTES.txt that
hive-operator#753 and kafka-operator#1013 landed per repo, generated instead so
the remaining twelve do not need hand-written copies.

The template needs no new configuration. The three fields it varies on already
exist and are already used the same way by README.md.j2:

  operator.pretty_string                                  the product name
  operator.product_string                                 the documentation slug
  operator.hub_component_slug | default(product_string)    the Hub slug, which
                                                           only spark-k8s overrides
  operator.config.has_product | default(true)              the gate below

commons, listener and secret have has_product false, so they get different prose
and no Hub link, because they own no product custom resource and have no Hub
component page. Their pretty_string already ends in "Operator", so the sentence
uses chart_title for them and would otherwise read "the Stackable operator for
Stackable Secret Operator".

Output is byte-identical to the NOTES.txt already merged in hive-operator and
kafka-operator, and to the files in the open trino-operator and zookeeper-operator
pull requests, so the next rollout adds the file to twelve charts and shows no
diff for those four.
@lfrancke
lfrancke marked this pull request as ready for review September 8, 2026 09:06
@lfrancke
lfrancke added this pull request to the merge queue Sep 8, 2026
Merged via the queue into main with commit 46be141 Sep 8, 2026
2 checks passed
@lfrancke
lfrancke deleted the push-sxyorkmlyklx branch September 8, 2026 09:07
@lfrancke lfrancke moved this to Development: Done in Stackable Engineering Sep 8, 2026
@lfrancke lfrancke moved this from Development: Done to Acceptance: In Progress in Stackable Engineering Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Acceptance: In Progress

Development

Successfully merging this pull request may close these issues.

2 participants