infra/otc-metadata-rework
14
0
Fork 16
Code Issues 5 Pull Requests 6 Actions Packages Releases 1 Wiki Activity

Adding metadata for css koosearch api-ref and umn #18

Merged
zuul merged 3 commits from vpruthi/otc-metadata-rework:css_koosearch_metadata into main 2025-07-04 11:33:11 +00:00
Conversation 10 Commits 3 Files Changed 2
+26
2 changed files with 26 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
otc_metadata/data/documents/css-koosearch-api-ref.yaml
+13
View File
@@ -0,0 +1,13 @@
---
hc_location: koosearch-api/css
html_location: docs/css/koosearch-api-ref
link: /cloud-search-service/koosearch-api-ref/
rst_location: doc/koosearch-api-ref/source
vpruthi marked this conversation as resolved Outdated
sgode commented 2025-07-04 07:54:55 +00:00
Outdated
Review
Copy Link
Copy Source

Please put this under doc/koosearch-api-ref

Same for the others

Please put this under doc/koosearch-api-ref Same for the others
vhasko commented 2025-07-04 07:57:02 +00:00
Outdated
Review
Copy Link
Copy Source

please change to doc/koosearch-api-ref/source

please change to doc/koosearch-api-ref/source
service_type: css
title: Koosearch API Reference
type: koosearch-api-ref
cloud_environments:
- name: eu_de
visibility: internal
vpruthi marked this conversation as resolved Outdated
sgode commented 2025-06-25 07:20:56 +00:00
Outdated
Review
Copy Link
Copy Source

This will instantly make the document public visible and linked on docs.otc.t-systems.com, so in case we don’t have a documentation on GitHub yet it will result in a 404. Are you sure you want that? Else just put it to internal here

This will instantly make the document public visible and linked on docs.otc.t-systems.com, so in case we don't have a documentation on GitHub yet it will result in a 404. Are you sure you want that? Else just put it to internal here
vpruthi commented 2025-07-03 08:57:54 +00:00
Outdated
Review
Copy Link
Copy Source

Thank you Sebastian for your feedback, you are right, for now it will be best to set visibility to internal and later change to public when documents are ready to be published on prod. :)

Thank you Sebastian for your feedback, you are right, for now it will be best to set visibility to internal and later change to public when documents are ready to be published on prod. :)
pdf_visibility: public
pdf_enabled: true
otc_metadata/data/documents/css-koosearch-umn.yaml
+13
View File
@@ -0,0 +1,13 @@
---
hc_location: koosearch-usermanual/css
html_location: docs/css/koosearch-umn
link: /cloud-search-service/koosearch-umn/
rst_location: doc/koosearch-umn/source
vpruthi marked this conversation as resolved Outdated
vhasko commented 2025-07-04 07:57:19 +00:00
Outdated
Review
Copy Link
Copy Source

please change to doc/koosearch-umn/source

please change to doc/koosearch-umn/source
service_type: css
title: Koosearch User Guide
type: koosearch-umn
cloud_environments:
- name: eu_de
visibility: internal
vpruthi marked this conversation as resolved Outdated
sgode commented 2025-06-25 07:21:01 +00:00
Outdated
Review
Copy Link
Copy Source

same here

same here
vpruthi commented 2025-07-03 08:58:19 +00:00
Outdated
Review
Copy Link
Copy Source

updated to internal

updated to internal
pdf_visibility: public
pdf_enabled: true