[BREAKING_CHANGE] Added support for multiple variable values for the same connector

[CherfaElyes]

Specification

Currently, it is possible to define connector variables values as follows:

resources:
  <host_id>:
    attributes:
      host.name: <hostname>
      host.type: linux
    protocols:
      ssh:
        username: <username>
        password: <password>
    variables:
      <connectorId>:
        <variableName>: <variableValue>

This does not allow to use the same connector more than once. To remedy, we would like to implement the following configuration in order to be able to use the same connector many times with different connector variables values:

  additionalConnectors:
    <CustomConnectorId1>: 
      uses: <ConnectorId> # If not specified, the default is the key name
      variables:
        <VariableName>: <VariableValue>
      force: false # default true
    <CustomConnectorId2>: 
      uses: <ConnectorId> # If not specified, the default is the key name
      variables:
        <VariableName>: <VariableValue>
      force: false # default true

To do

• 1. Update the resourceConfig to take into consideration the additionalConnectors section.
• 2. Make all the necessary changes in the engine & the agent to adapt.
  • 2.1 Add AdditionalConnectorsConfig & deserialize them
  • 2.2 Update ConnectorTemplateLibraryParser to handle the changes.
• 3. Adapt unit tests.
• 4. Test the changes on MetricsHub.
• 5. Update the connectors maven plugin to correctly display connector variables and generate metricshub.yaml.
  Display the new additional connectors configuration metricshub-connector-maven-plugin#63
• 6. Update MetricsHub example to give an example of the additionalConnectors section.
• 7. Modify MetricsHub documentation to update how to configure connector variables.
• 8. Update metricshub-community connectors
  Document default connector variables metricshub-community-connectors#128
• 9. Add parameterized tag to connectors with variables
  Add Parameterized tag to LinuxProcess, LinuxService, WindowsProcess & WindowsService  metricshub-community-connectors#138
• 10. Modify MetricsHub schema in schemastore.
• 11. Add CLI options to additional connectors and connector variables
  Add the ability to specify connector variables in the metricshub CLI #357