Hasko, Vladimir 62a98b6a2a removing the mistakely merged content for DLI dev guide dli_dev_0104_version
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com>
Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
2024-01-09 16:18:17 +00:00
2022-10-19 06:33:38 +00:00
2023-03-22 11:42:43 +00:00
2023-03-22 11:42:43 +00:00
1
2023-10-17 05:08:37 +00:00
2022-03-08 10:25:35 +01:00
2024-01-03 08:54:16 +00:00
2022-05-03 05:20:12 +00:00
2022-04-27 16:05:48 +00:00
2024-01-03 09:18:55 +00:00

doc-exports

Repository to track document exports, not for public use

Document sources (in HTML) are placed under docs//

In the there are files docs_.yaml that describe required data for the particular document. For all of the documents configured in those files conversion from HTML to RST will be attempted. In addition to that a patch file (changes in the RST format) will be generated.

Automatic pull request proposal

Change for any of the documents configured in the docs_.yaml would trigger job to propose corresponding changes to the target repository. This is implemented in the following way:

  • HTML content from the pull request will be converted with the latest conversion script (otc_doc_convertor) to RST (new)

  • HTML content for the same document from current main branch with the corresponding version of the conversion script will be converted to RST (base).

  • New state is compared against base and corresponding patch file is generated

  • Resulting patch file is force-applied in the target repository (skipping all conflicts) and PR is created

Description
Open Telekom Cloud Doc Exports
Readme 334 MiB
Languages
Python 87.3%
Jinja 12.7%