wangdengke2 a15d5e5f49 dds_api
Reviewed-by: Gladkov, Maksim <mgladkov@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: wangdengke2 <wangdengke2@huawei.com>
Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
2025-08-26 10:11:15 +00:00
2025-08-26 10:11:15 +00:00
2025-06-17 08:22:19 +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
2023-10-17 05:08:37 +00:00
2025-05-05 07:44:03 +00:00
2022-03-08 10:25:35 +01:00
2024-09-28 19:01:52 +00:00
2022-05-03 05:20:12 +00:00
2022-04-27 16:05:48 +00:00
2024-10-22 11:17:42 +00:00
2024-10-22 11:17:42 +00:00
2025-07-24 16:57:37 +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 Apache-2.0 768 MiB
Languages
Python 87.7%
Jinja 12.3%