ConfigSeder 2.5 release is focusing on stability and improved user experience through bugfixing. Never the less we also provide some nice features we would like to present in the following.

New Features

Booleans, Integers or Numbers

Typically all configuration values are strings. But for some values, you would like to have more type safety, because they are used as integers for port numbers, or as booleans for enabling features or maybe as percentiles for your mathematical / statistical configuration.
Besides the existing text based datatypes, you can now choose to add numbers, integers or booleans.

Be aware that if you use these new types you’ll need to update all your clients (e.g. Java clients for MicroProfile, Spring, Java) or GO clients

Usability improvements

Have you ever clicked on a link without saving your changes and you’ve lost your changes? With release 2.5, the UI prevents loosing your changes by asking for confirmation before leaving an unsaved form. Additionally, all links can now be opened in separate tabs.

Features and improvements

• ConfigurationValueType: Integer, Number and Boolean #109
• API Key should have a default name based on the selection of the ConfigurationGroup #430
• Enhanced feedback when using templating without dateTime set in request.json #480
• Offer links as routing and link #564
• API based on type instead of feature #574
• Templating is now possible with configurationGroupId as well as with configurationGroupKey #591
• Form with unsaved changes asks for save or cancel. #594
• Changed history view for assembly #595
• Forced logout on unexpected error #582
• Added support for copying assemblies #586
• Updated SQL Server driver to version 7.2 #643

Bugfixes

• Unclear message if one of the resources cannot be loaded #584
• Fonts should be provided by ConfigSeeder itself  #603
• “Add” button cropped in german. Switch to icons  #612
• Delete changed assembly asks for confirmation to keep changes  #613
• Double scrollbars, although not needed  #614
• No space for “create assembly” button (icon needed)  #616
• Error when importing into non-existing Configuration Group #617
• Missing information on API Key – renew screen  #620
• Fix error when importing template files with configuration node strategy “replace” #621
• Export / Import of assemblies leads to invalid data #622
• User with no “tenant all” privilege is not able to export. #623
• Vulnerabilities found during build #624
• Upon deleting a single value the full node is deleted #631
• Environment not loaded from the backend #632
• Databinding issue when going from CNVO to preview #639
• ConfigurationValueType: Boolean should toggle state immediately on click 642
• After bulk operation, selection is lost 646
• After cloning selection is not applied on the new created values 647
• After fixing conflicts using bulk operations, conflict check is not performed. 648
• After restoring, wrong assembly is loaded 650
• Renewing API Key leads to a new name 651
• ConfigurationGroups list loaded, although not needed 658