Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Helm Chart v XXX

Single Page Application V 0.3.0 - New Features

UI changes

Scrollable header section in component and configuration: Components and configurations now have a scrollable header section so that it disappears when scrolling down.

Externalize SSO/Authentication configuration

The authentication provider configuration was removed from the UI and is now configured via environment variables (see list of fields here). The fields themself did not change so can its basically the same as it was in the UI.

This configuration now also applies for the whole application and is no longer specific to a space.

Externalize Space configuration

The management of spaces was removed from the REST api and is now only managed via environment variable. The spaces defined this way will be created or if they already exist updated during start up of the application. Existing spaces in the database that are not defined this way will be ignored by the application.

The space identifier (previously called spaceId, now called spaceKey) can be specified as part of the environment variable SPACES_DATA (see below, and listed in the full environment variable list here). The space key can only contain alphanumeric characters, hyphens and underscores.

The spaceId was previously also used as the database name for the space. The database name is now separate. If the specified database exists it will be used by the application for this space, if not the application tries to create it.

The application expects the SPACES_DATA environment variable to be a json string. The json string contains an array of space definitions. Example:

[
    {
        "key": "ExampleKey",
        "title": "An example title",
        "databaseName": "CDCM-database-name"
    },
    {
        "key": "AnotherExampleKey",
        "title": "An different title",
        "databaseName": "Other-db"
    }
]

Write TRS stream

Implemented an endpoint to provide a tracked resource set - based change log which tracks creation, modification and deletion of components and configurations. Changes on configuration items are tracked as a modification of a configuration. The change log contains links to the OSLC resource representation of the concept.

Bug fixes

Miscellaneous

  • Implemented additional logging on level “info” for the OAuth1.0a configuration process

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.