Skip to content

Expose OSDU specific meta data to manifest

Laurent Deny requested to merge ldeny/improve_xmetadata_manifest into main

Type of change

  • Bug Fix
  • Feature

Does this introduce a change in the core logic?

  • [Yes]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Updates description?

Provide a solution for #23 (closed).

Every xtrameta data with the key "osdu/path1/path2" and the value "value" will be transformed into a JSON property corresponding to the { "path1" : { "path2" : "value" } }if such a path is defined in the corresponding OSDU type shema, else it will be added to the OSDU type as "data": { "ExtensionProperties" : { "path1/path2" : "value } }. Xtramedata whose key does not start with OSDU will be ignored.

Merge request reports