Restore deprecated NotificationsConfig.Region field #4299
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tracking issue
Fixes #3070
Fixes #4296
Describe your changes
This change
NotificationConfig.Region
field from the flyte-core configmap template. This was removed in fix helm notifications config #4055. While the config struct field has a comment indicating deprecated, the alternativeNotificationConfig.AWSConfig.Region
is not consumed everywhere yet. It is not safe to stop populating this field yet, and is in fact required for all existing versions of flyteadmin to use NotificationsProcessor and Emailer. The deprecated field is only populated in the absence of theaws
block.NotificationConfig.AWSConfig.Region
and only fallback to the deprecated field if necessary.Testing
I ran through a couple EKS and GCP helm templating scenarios to verify the fix correctly populates the deprecated region field if used and no other changes otherwise.
EKS with deprecated region field
Before:
After:
EKS with AWS region field
GCP
Check all the applicable boxes