Version 13.1.0 Release Notes

September 12th, 2024

Console

Manage iFrame extensions from Console UI

We are constantly enriching our ecosystem by bringing new features to our Platforge Extensibility Kit: from now on, you will be able to add iFrame extensions in Console directly via a dedicated "Extensions" manager, available - for Company Owners - at Company level in the Platforge section!

Start customizing your Console by adding your first iFrame extension: simply select the Area and Sidebar section from the available options and add the entry URL you want to make visible to your users!

To discover more, head to the Extensions documentation page.

Compare changes feature available for non-Enhanced Projects

Already present for all Enhanced projects, this feature has now been brought to non-Enhanced projects as well.

Furthermore, the resources in the compare interface will now be differentiated into 3 different categories: Workload, Configmaps and Custom Resources.

For more information, visit the related documentation page.

info

For implementation requirements it has been modified the previous API interface of the compare changes feature.

If necessary, the new interface documentation can be found directly through the console API Portal.

Improvements

Enhanced Workflow as Default in Project Creation

The Enhanced Workflow is now enabled by default when creating new Projects, with the toggle switched on automatically in the Project creation flow.

info

Please note that, starting from v14.0.0, new Projects will exclusively be created with the Enhanced Workflow, fostering better performances and leveraging features such as GitOps, Custom Orchestrators and quicker configuration save time!

For more information about Enhanced Project Workflow, visit the related documentation page.

New Apply Extension Body Schema

The PUT /api/extensibility/tenants/{tenantId}/extensions used to register extensions supports a new body format that is clearer and simpler to use, along with the manifest to be sent using the miactl extensions apply command.

tip

The legacy body format is still supported until the next minor version, we strongly suggest to start using the new schema following the instructions below as soon as possible. In addition, make sure to upgrade miactl to version 0.15 to make use of the new format.

Migration guide from legacy to new apply body format

Starting from the following legacy format as example:

{
  "extensionId": "my-extension-id",
  "name": "My Extension",
  "entry": "https://example.com/",
  "extensionType": "iframe",
  "contexts": ["project"],
  "description": "Example Extension",
  "permissions": [],
  "routes": [
    {
      "destinationPath": "/",
      "icon": {
        "name": "PiProjectorScreenChartLight"
      },
      "id": "my-route",
      "labelIntl": {
        "en": "My Extension",
        "it": "La mia estensione"
      },
      "order": 200.0,
      "locationId": "project",
      "parentId": "my-menu-group"
    },
    {
      "id": "my-menu-group",
      "labelIntl": {
        "en": "My Menu Group",
        "it": "Il mio gruppo menu"
      },
      "locationId": "project",
      "renderType": "category",
      "order": 100.0,
    },
  ]
}

it is possible to migrate to new format properties following the mapping explained by this table:

New schema properties	Legacy schema properties
extensionId	extensionId
name	name
entry	entry
type	extensionType
activationContexts	contexts
description	description
permissions	permission
destination.id	mainRoute.locationId
destination.path	mainRoute.destinationPath
iconName	mainRoute.icon.name
menu.id	mainRoute.id
menu.labelIntl	mainRoute.labelIntl
menu.order	mainRoute.order
category.id	mainRoute.parentId
category.labelIntl	categoryRoute.labelIntl
category.order	categoryRoute.order

where:

• mainRoute is the last route in the routes legacy properties that does not define renderType, so the route with my-route ID.
• categoryRoute is the last route in the routes legacy properties that defines renderType as category. This is the custom category registered with the extension and it could be omitted in the request, in fact in this case the new category properties will have only the id defined taken by the mainRoute.parentId. In the example above there is a custom category and corresponding to the route with my-menu-group ID.

After migration the new body format is the following:

{
  "extensionId": "my-extension-id",
  "name": "My Extension",
  "entry": "https://example.com/",
  "type": "iframe",
  "activationContexts": ["project"],
  "description": "Example Extension",
  "permissions": [],
  "destination": {
      "id": "project",
      "path": "/",
  },
  "iconName": "PiProjectorScreenChartLight",
  "menu": {
    "id": "my-route",
    "labelIntl": {
      "en": "My Extension",
      "it": "La mia estensione"
    },
    "order": 200.0,
  },
  "category": { 
      "id": "my-menu-group",
      "labelIntl": {
        "en": "My Menu Group",
        "it": "Il mio gruppo menu"
      },
      "order": 100.0,
  }
}

Bug Fix

This version addressed the following bugs:

• fixed a bug on the Azure Key Vault provider that prevented the retrive of more than 25 keys from the vault;
• The Orchestrator Generator timeout limit has been increased to 15s to better handle requests;
• Marketplace search is now more accurate when searching the name of a resource.

Fast Data

Fast Data Runtime Management

Bug Fix

It has been fixed an issue that prevented the feedback on the reducing step of Fast Data Control Plane frontend from being displayed correctly if a projection belongs to more than one single view pipelines.

Marketplace

Marketplace Updates

API Portal

The new version 2.1.0 of the API Portal is available!

New Features

Added support to OAuth 2.0 Authorization customizations

Bug fix

• Fixed scroll behavior with bottom elements
• Edited warning note in download modal

Swagger Aggregator

The new version 3.8.0 of the Swagger Aggregator is available!

New Features

Added support to OAuth 2.0 Authorization customizations

CRUD Service

The new version 7.1.0 of the CRUD Service is available!

New Features

Added the possibility to specify where crypt_shared MongoDB dynamic library is located through the new, optional environment variable CRYPT_SHARED_LIB_PATH

Improvements

• Enforce quoting all strings in CSV export to prevent issues with delimiter character

Bug fix

• Fixed a crash caused by the service being configured to run with the CSFLE feature enabled and a Mongo View defined alongside the collections models

How to update your Console

For self-hosted installations, please head to the self hosted upgrade guide or contact your Mia-Platform referent and upgrade to Console Helm Chart v13.7.1.