Tim Möhlmann 91bc71db74

fix(instance): add web key generation to instance defaults (#9815) ...

# Which Problems Are Solved

Webkeys were not generated with new instances when the webkey feature
flag was enabled for instance defaults. This would cause a redirect loop
with console for new instances on QA / coud.

# How the Problems Are Solved

- uncomment the webkeys section on defaults.yaml
- Fix field naming of webkey config

# Additional Changes

- Add all available features as comments.
- Make the improved performance type enum parsable from the config,
untill now they were just ints.
- Running of the enumer command created missing enum entries for feature
keys.

# Additional Context

- Needs to be back-ported to v3 / next-rc

Co-authored-by: Livio Spring <livio.a@gmail.com>

2025-04-29 14:54:53 +00:00

..

integration_test

fix: remove action feature flag and include execution (#9727)

2025-04-28 11:24:50 +02:00

converter_test.go

fix: remove action feature flag and include execution (#9727)

2025-04-28 11:24:50 +02:00

converter.go

fix(instance): add web key generation to instance defaults (#9815)

2025-04-29 14:54:53 +00:00

feature.go

feat: specify login UI version on instance and apps (#9071)

2024-12-19 10:37:46 +01:00

server.go

feat: api v2beta to api v2 (#8283)

2024-07-26 22:39:55 +02:00