You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #1472 (comment), it was clarified that if a user configured a fixed module version, and this version runs out of support, the module becomes unmanaged.
Things that need to be clarified:
how do we determine if a version is unsupported?
how to distinguish this from the case where a version is configured that doesn't exist at all (check cannot be based on the sheer absence of a ModuleTemplate)
how to announce a deprecation warning and sunset date?
info needs to be available somewhere and other team, i.e. hasslehoff, will need to be informed to display this to the user
see proposed AC... is it good practice that we change spec of the field, or are we keeping the spec as is and just update the status?
what is the appropriate state to display, Unmanaged, Unsupported, SupportCeased?
Reasons
Module versions cannot be supported indefinitely.
Acceptance Criteria
When KymaCR contains a module with an unsupported version
KymaCR .spec.modules[].managed is set to false
Feature Testing
No response
Testing approach
No response
Attachments
No response
The text was updated successfully, but these errors were encountered:
Description
In #1472 (comment), it was clarified that if a user configured a fixed module version, and this version runs out of support, the module becomes unmanaged.
Things that need to be clarified:
Reasons
Module versions cannot be supported indefinitely.
Acceptance Criteria
.spec.modules[].managed
is set tofalse
Feature Testing
No response
Testing approach
No response
Attachments
No response
The text was updated successfully, but these errors were encountered: