Skip to content
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

[BUG] Removed NotificationsConfig.Region field still referenced #4296

Closed
2 tasks done
andrewwdye opened this issue Oct 25, 2023 · 3 comments · Fixed by #4299
Closed
2 tasks done

[BUG] Removed NotificationsConfig.Region field still referenced #4296

andrewwdye opened this issue Oct 25, 2023 · 3 comments · Fixed by #4299
Assignees
Labels
bug Something isn't working

Comments

@andrewwdye
Copy link
Contributor

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

  1. 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
  2. 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
@andrewwdye andrewwdye added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers labels Oct 25, 2023
@eapolinario eapolinario removed the untriaged This issues has not yet been looked at by the Maintainers label Oct 26, 2023
@adarsh-jha-dev
Copy link
Contributor

Hey @andrewwdye , could you please assign me this issue? I'd like to work on this

@adarsh-jha-dev
Copy link
Contributor

adarsh-jha-dev commented Oct 27, 2023

Hey @pingsutw , i have raised a PR regarding this issue, could you please have a look at it and let me know if the changes are relevant ?

@andrewwdye
Copy link
Contributor Author

Hi @adarsh-jha-dev I forgot to cross reference here, but this was fixed by #4299

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants