netdata_netdata/integrations/templates
Fotis Voutsas effe8e6f26
files movearound (#17653)
2024-05-15 10:01:46 +03:00
..
overview add Okta SSO integration (#17351) 2024-04-10 12:00:48 +03:00
setup Bugfix in integrations/setup/template (#16142) 2023-10-06 11:41:17 +03:00
README.md Add initial tooling for generating integrations.js file. (#15406) 2023-08-01 17:23:16 -04:00
alerts.md Introduce stringify function for integrations (#16140) 2023-10-06 11:09:46 +03:00
integrations.js Add initial tooling for generating integrations.js file. (#15406) 2023-08-01 17:23:16 -04:00
metrics.md Add integrations JSON file for website usage. (#15959) 2023-10-18 11:30:30 -04:00
overview.md add Okta SSO integration (#17351) 2024-04-10 12:00:48 +03:00
platform_info.md Update platform_info.md 2023-08-21 17:58:50 +03:00
related_resources.md Add initial tooling for generating integrations.js file. (#15406) 2023-08-01 17:23:16 -04:00
setup.md files movearound (#17653) 2024-05-15 10:01:46 +03:00
troubleshooting.md Assorted fixes for integrations templates. (#15702) 2023-08-02 10:01:04 -04:00

README.md

This directory contains templates used to generate the integrations.js file.

Templating is done using Jinja2 as a templating engine. Full documentation can be found at https://jinja.palletsprojects.com/en/ (the Template Designer Documentation is the relevant part for people looking to edit the templates, its not linked directly here to avoid embedding version numbers in the links).

The particular instance of Jinja2 used has the following configuration differences from the defaults:

  • Any instances of curly braces in are replaced with square brackets (so instead of {{ variable }}, the syntax used here is [[ variable ]]. This is done so that templating commands for the frontend can be included without having to do any special escaping for them.
  • trim_blocks and lstrip_blocks are both enabled, meaning that the first newline after a block will be removed, as will any leading whitespace on the same line as a block.

Each markdown template corresponds to the key of the same name in the integrations objects in that file. Those templates get passed the integration data using the name entry, plus the composed related resource data using the name rel_res.

The integrations.js template is used to compose the final file. It gets passed the JSON-formatted category and integration data using the names categories and integrations respectively.