Skip to main content

Mapping Extensions

Introduction​

The default way to map your data to Port is by using JQ JSON processor to map and transform your data to Port entities.

However, in some cases you may want to map data to Port in a way that default JQ mapping is not enough.

Possible Use Cases:

  • Map your repository README.md file contents into Port;
  • Check if a specific file exists in your repository;
  • Check if a specific string exists in your repository;
  • Check if a specific version of a package is used in your repository;
  • Check if a CI/CD pipeline is configured in your repository;

Mapping file content into Port​

In the following example you will define and export your Azure Devops projects and their README.md file contents to Port:

Repository blueprint
{
  "identifier": "azureDevopsRepository",
  "title": "Repository",
  "icon": "AzureDevops",
  "schema": {
    "properties": {
      "url": {
        "title": "URL",
        "format": "url",
        "type": "string",
        "icon": "Link"
      },
      "readme": {
        "title": "README",
        "type": "string",
        "format": "markdown",
        "icon": "Book"
      }
    },
    "required": []
  },
  "mirrorProperties": {},
  "calculationProperties": {},
  "aggregationProperties": {},
  "relations": {}
}

As we can see one of the properties is of type markdown, this means that we need to map the README.md file contents into Port.

To do so, we will use the file:// prefix with the path of the file to tell the Azure Devops exporter that we want to map the contents of a file into Port.

  - kind: repository
    selector:
      query: 'true'
    port:
      entity:
        mappings:
          identifier: .project.name + "/" + .name
          title: .name
          blueprint: '"azureDevopsRepository"'
          properties:
            url: .url
            readme: file://README.md