adding rfs metadata

Reviewed-by: Gode, Sebastian <sebastian.gode@t-systems.com>
Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>

otc_metadata/data/documents/rfs-api-ref.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: api/rfs
+environment: internal
+html_location: docs/rfs/api-ref
+link: /resource-formation-service/api-ref/
+pdf_name: rfs-api-ref
+rst_location: api-ref/source
+service_type: rfs
+title: API Reference
+type: api-ref

otc_metadata/data/documents/rfs-umn.yaml

@@ -0,0 +1,10 @@
+---
+hc_location: usermanual/aos
+environment: internal
+html_location: docs/rfs/umn
+link: /resource-formation-service/umn/
+pdf_name: rfs-umn
+rst_location: umn/source
+service_type: rfs
+title: User Guide
+type: umn

otc_metadata/data/services/rfs.yaml

@@ -0,0 +1,16 @@
+---
+environment: internal
+repositories:
+- environment: internal
+  repo: docs/resource-formation-service
+  type: gitea
+- environment: public
+  repo: opentelekomcloud-docs/resource-formation-service
+  type: github
+service_category: application
+service_title: Resource Formation Service
+service_type: rfs
+service_uri: resource-formation-service
+teams:
+- name: docs-orchestration-rw
+  permission: write