With Release 2.9.0 of ConfigSeeder Management and Release 1.0.0 of ConfigSeeder Kubernetes Connector Kubernetes functionalities like ConfigMaps and Secrets are now covered.

Highlight Features

Kubernetes Connector

Kubernetes Connector has now reached productive status. With Kubernetes Connector 1.0 it’s not only possible to generate API keys as secrets, but also to update config maps and secrets. A dedicated article will describe our best practices.

API keys with owners

API keys can now be assigned to another owner. This helps when team members are leaving the team or have changed responsibilities.

Setup mode is more secure

Previously when running the application in setup mode anyone had the full privilege. This has now changed with the latest release. On startup, a secret is shown and prevents others from being able to do any malicious modification.

Feature and improvements

• Allow API key to be assigned to another owner. #601
• Allow uploading a license via copy & paste #606
• Assembly Types Secret: Key/Value Local & Referenced (Server) #797
• Extend setup mode to be also active with a “testing”-mode, but additional credential #789

• The warning dialog when revoking an API key should contain more details #781
• Audit Log: Housekeeping #788
• About Page: Add Info about used Database #817

Fixes

• Unexpected ConfigValue returned from ConfigSeeder #475
• License Statistics: Bug for Value Provider / Last access #793
• Issue when deleting environment with unsaved changes #798
• Changes cannot be saved. #816
• Error when entering only ‘validTo’ on API Key #818
• Text mismatch after creating API Key #819
• Missing “ALL” text on API key deletion #820
• Value search filter should not include non-visible texts #824
• Validation issues #825
• The key is not focused. Shortcut for creating new #826
• Changing Secured Flag should not lead to Conflict Detection #827
• Ctrl-Alt-C throws Exception #828
• In the about dialog only date should be shown #829