[FEATURE]Package integration as part of the CI Process

[YANG-DB]

Is your feature request related to a problem?

As part of the CI / Build process we would like to package the integrations into a versioned bundle of Integration-catalogs what can be loaded by the integration framework as a single unit (group).

What solution would you like?
The package integrations-catalog process will do the following :

packing workflow

For each integration catalog within the integrations folder:

- take the catalog description file
- the integration-catalog name and metadata appears in this catalog file
- For each integration resource within the catalog file:
- Take the integration config file which contains the integration metadata and details.

For Each integration:
- take the type field from the integration config file:

  "type": "logs",

Go to that file's schema section and copy the required mapping file name (log index template file in this case) and version:

  "components": [
    {
      "name": "communication",
      "version": "1.0.0"
    },
    {
      "name": "http",
      "version": "1.0.0"
    },
    {
      "name": "logs",
      "version": "1.0.0"
    }
  ],

And get their corresponding index_template mapping (log-1.0.0.mapping) file from the catalog schema mapping folder for that domain (Observability)

If other components appear in the component list (in our example http & communication also take them from the (Observability ) schema folder according to their version (1.0.0)

Add these components into the composed_of section in the type index_template mapping container (in our case log-1.0.0.mapping)

In the following way:

  "composed_of": [ "http-1.0.0.template", "communication-1.0.0.template"]
],

In addition this index_template can optionally also contain the alias instruction that was mentioned in the integration config:

  "type-alias": "logs-nginx",

This would produce the next part in the index_template output file:

    ...
      "aliases": {
      "logs-apache": {}
    },

This (index_template) schema file will reside in a schema folder within the integration folder in addition to the component template that appeared in the components section. They will be copied as-is from the (Observability ) catalog folder directly.

This concludes the preparation of the integration folder for being packaged in the integration-catalog archive.

---

Do you have any additional context?

• [FEATURE] Testing for integrations in CI #74
• [FEATURE]Migrate Integrations to catalog #69
• [FEATURE] Add CI for Integrations CLI #38