-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KIM Integration - redesign configuration after migration is done #1241
Comments
Blocked till migration is done. |
Following configuration values should be migrated to
We could consider moving:
Following values should be moved to other place (possible section with timeouts - there are more timeouts settings scattered):
Following values should be removed (double check before actual removal):
Removal is blocked until |
|
When we use KIM only, provisioner is no longer used, we need to simplify and unify configuration.
To many steps we pass separately
input.Config
andbroker.KimConfig
objects.Phase 1 AC: 12.2024
Phase 2 AC: 01.2025
provisioner
related settings (this is in scope of different ticket)kim
sectionThe text was updated successfully, but these errors were encountered: