Readme Generator For Helm

• Autogenerate Helm Charts READMEs' tables based on values YAML file metadata.
• Autogenerate an OpenAPI compliant JSON schema defining the values.yaml structure of the Helm Chart. The file generated will be a JSON file formatted according to the OpenAPIv3 SchemaObject definition.

How it works

The tool expects some metadata for the descriptions in the provided values.yaml file. It will parse and check the metadata against the real values. If the metadata is consistent with the real values, it will generate and insert the values table into the provided README.md file. If the metadata is not correct, it will print the full list of errors. It checks whether there is metadata for non-existing values or there is missing metadata for an existing value.

The table that will be inserted into the readme.md will have the following structure:

1## Parameters
2
3### Section 1 title
4
5| Name      | Description             | Default        |
6|:----------|:------------------------|:---------------|
7| `value_1` | Description for value 1 | `defaultValue` |
8| `value_2` | Description for value 2 | `defaultValue` |
9| `value_3` | Description for value 3 | `defaultValue` |
10
11### Section 2 title
12
13| Name      | Description             | Default        |
14|:----------|:------------------------|:---------------|
15| `value_1` | Description for value 1 | `defaultValue` |
16| `value_2` | Description for value 2 | `defaultValue` |
17| `value_3` | Description for value 3 | `defaultValue` |
18
19...

The number of # characters needed for the section titles is dynamically calculated, and the title of the Parameters section can be configured via the configuration file. The README.md file with a ## Parameters section must be created before running the tool, the Parameters section should have two # or more symbols.

Requirements

The project has been developed and tested with node version 22.x.

Install

Execute the following commands to install the tool:

1git clone https://github.com/bitnami/readme-generator-for-helm
2npm install ./readme-generator-for-helm

Depending on how you installed NodeJS in your system, you may need to modify your PATH environment variable to be able to execute the tool.

Single Binary

Execute the following commands to create a single executable binary for the tool:

1git clone https://github.com/bitnami/readme-generator-for-helm
2cd ./readme-generator-for-helm
3npm install
4npm install -g @yao-pkg/pkg
5pkg . -o readme-generator-for-helm

Test

We use Jest to implement the tests. In order to test your changes, execute the following command:

1npm run-script test

Lint

After modifying the code execute the following command to pass the linter:

1npm run-script lint

Basic usage

1Usage: readme-generator [options]
2
3Options:
4  -v, --values <path>  Path to the values.yaml file
5  -r, --readme <path>  Path to the README.md file
6  -c, --config <path>  Path to the config file
7  -s, --schema <path>  Path for the OpenAPI Schema output file
8  --version            Show Readme Generator version
9  -h, --help           display help for command

values.yaml Metadata

For the tool to work, you need to add some metadata to your values.yaml file.

By default we use a format similar to Javadoc, using @xxx for tags followed by the tag structure.

The following are the tags supported at this very moment:

• For a parameter: ## @param fullKeyPath [modifier?] Description.
• For a section: ## @section Section Title".
• To skip an object and all its children: ## @skip fullKeyPath Description?.
• To add a description for an intermediate object (i.e. not final in the YAML tree): ## @extra fullkeyPath Description.

All the tags as well as the two initial # characters for the comments style can be configured in the configuration file.

[!IMPORTANT] tags' order or position in the file is NOT important except for the @section tag. The @section that will include in the section all the parameters after it until a new section is found or the file ends.

The modifier is optional and it will change how the parameter is processed. Several modifiers can be applied by separating them using commas (,). When affecting the value, the last one takes precedence.

Currently supported modifiers:

• [array] Indicates that the value of the parameter must be set to [].
• [object] Indicates that the value of the parameter must be set to {}.
• [string] Indicates that the value of the parameter must be set to "".
• [nullable] Indicates that the parameter value can be set to null.
• [default: DEFAULT_VALUE] Sets the default value to DEFAULT_VALUE.

The modifiers are also customizable via the configuration file.

In case you are adding a custom modifier to a parameter that does not have value in the values file you must add one of the supported modifiers as last modifier.

Example:

Values file

1# @param noDefaultValue [number, nullable] Description
2# noDefaultValue: 1

Custom configuration snippet:

1{
2  ...
3    "modifiers": {
4    "array": "array",
5    "object": "object"
6    "string": "string"
7    "nullable": "nullable",
8    "number": "number"
9  },
10  ...
11}

Configuration file

The configuration file has the following structure:

1{
2  "comments": {
3    "format": "##"                               <-- Which is the comments format in the values YAML
4  },
5  "tags": {
6    "param": "@param",                           <-- Tag that indicates a parameter
7    "section": "@section",                       <-- Tag that indicates a section
8    "descriptionStart": "@descriptionStart",     <-- Tag that indicates the beginning of a section description
9    "descriptionEnd": "@descriptionEnd",         <-- Tag that indicates the end of a section description
10    "skip": "@skip",                             <-- Tag that indicates the object must be skipped
11    "extra": "@extra"                            <-- Tag to add a description for an intermediate object
12  },
13  "modifiers": {
14    "array": "array",                            <-- Modifier that indicates an array type
15    "object": "object"                           <-- Modifier that indicates an object type
16    "string": "string"                           <-- Modifier that indicates a string type
17    "nullable": "nullable"                       <-- Modifier that indicates a parameter that can be set to null
18  },
19  "regexp": {
20    "paramsSectionTitle": "Parameters"           <-- Title of the parameters section to replace in the README.md
21  }
22}

Pre-commit

Add this to your .pre-commit-config.yaml:

1- repo: https://github.com/bitnami/readme-generator-for-helm
2  rev: "main"
3  hooks:
4    - id: helm-readme-generator
5      # in order to run helm-readme-generator only once
6      pass_filenames: false
7      always_run: true
8      # default args are [--readme=chart/README.md, --values=chart/values.yaml]
9      args: [--readme=path/to/README.md, --values=path/to/values.yaml]

Versions

2.8.0

Descriptions now discard only a single whitespace. This way, code blocks can use proper indentation.

2.4.0

Add descriptionStart and descriptionEnd config options (default tags: @descriptionStart and @descriptionEnd) to allow text block upfront each section table in README.md. When changing the tag values for these, ensure to not being conflicted with section config option.

If you are using a customized configuration file, please add the new default tags to prevent any incorrect behavior.

2.0.0

The -m (--metadata) option has been renamed to -s (--schema) in order to properly identify what it generates.

License

Copyright © 2025 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.