Release 2.4.2 has put it’s main focus on easy integration of ConfigSeeder OS-Connector with ConfigSeeder Management. You can now easily create assemblies containing static or template based configuration files. There is no reason anymore to not bring configurations to a central place, our OS-Connector can handle it.

New Features

Assemblies

Assemblies offer an easy way how to manage your different kinds of configuration files. Using the new templating mechanism, you can place variables in your configuration file and replace them with centrally managed values.

Export and Import

• 

• 

With version 2.4.0 we offer simple ways how to export all values from your whole tenant or from single configuration groups. On import you can decide yourself which values should be kept, merged or fully replaced.

Additional features and improvements

• Implemented ConfigurationValueAssembly (Server) #492
• Implemented ConfigurationValueAssembly (Client) #558
• Design ConfigurationValueAssembly (UX) #528
• Tenant / Configuration Group Export #560
• Tenant / Configuration Group Import #561
• ConfigurationValueType: Configuration Group #563
• User Agent License Check #555
• Static login without OIDC #572
• API Key for real users #573
• Added details about including and exclusive of date and version #583

Bugfixes

• Change of secured flag does not need to trigger conflict check #559
• Exporting Data is not possible with API Keys #567
• Environment list is not loaded anymore #576
• Upon update of a configuration value, version is not passed #577
• Cannot edit configuration node key after cloning new entry #581
• Filter leads to reverted values #585
• Wrong error message when saving protected configuration nodes #590
• Sorting of configuration groups not alphabetically #592