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
The NotificationsConfig.Region field is no longer populated by the flyte-core chart template after this change in flyte 1.10; however, this code still assumes it's populated in two places (Emailer, NotificationsProcessor). This causes admin to crash on start when either of these functions are enabled.
As a solution we can either
Fully remove NotificationsConfig.Region from its struct and all references to it. This would complete the deprecation and continue on the path of a breaking change that we've already gone down in 1.10
Bring back NotificationsConfig.Region and follow a deprecation/removal path in the future
Expected behavior
It's possible to configure Emailer and/or NotificationsProcessor such that admin doesn't crash
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
Describe the bug
The NotificationsConfig.Region field is no longer populated by the flyte-core chart template after this change in flyte 1.10; however, this code still assumes it's populated in two places (Emailer, NotificationsProcessor). This causes admin to crash on start when either of these functions are enabled.
As a solution we can either
NotificationsConfig.Region
from its struct and all references to it. This would complete the deprecation and continue on the path of a breaking change that we've already gone down in 1.10NotificationsConfig.Region
and follow a deprecation/removal path in the futureExpected behavior
It's possible to configure Emailer and/or NotificationsProcessor such that admin doesn't crash
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: