Fotis Voutsas dfcf47e4cc Ιmplementation to add logs integrations (#18791) 1 month ago
..
overview dfcf47e4cc Ιmplementation to add logs integrations (#18791) 1 month ago
setup ff3cbef2b5 Bugfix in integrations/setup/template (#16142) 1 year ago
README.md 183bb1db19 Add initial tooling for generating integrations.js file. (#15406) 1 year ago
alerts.md f69ad3fbcc Introduce stringify function for integrations (#16140) 1 year ago
integrations.js 183bb1db19 Add initial tooling for generating integrations.js file. (#15406) 1 year ago
metrics.md d9c807e23c integrations make `<details>` open (#17895) 5 months ago
overview.md dfcf47e4cc Ιmplementation to add logs integrations (#18791) 1 month ago
platform_info.md 65a94cde3f Windows deploy metadata (#18733) 2 months ago
related_resources.md 183bb1db19 Add initial tooling for generating integrations.js file. (#15406) 1 year ago
setup.md dfcf47e4cc Ιmplementation to add logs integrations (#18791) 1 month ago
troubleshooting.md 0ab7826301 Remove the overview section from cloud notif. integrations (#18754) 1 month ago

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, it’s 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.