#7125 Send userinvite email Pull request opened by pmahindrakar-oss Why are the changes needed? The shared notification email contract currently supports only inline email content such as

subject

,

html_template

, and

text_template

. Some notification producers need to use provider-managed email templates identified by a template ID and a set of dynamic template parameters. The current contract does not model that use case cleanly. What changes were proposed in this pull request? This PR extends

flyteidl2.notification.EmailDeliveryTemplate

to support provider-backed email templates in a structured way. Changes in this PR: • Added a new

ProviderEmailTemplate

message with: •

template_id

•

template_data

• Added

provider_template

to

EmailDeliveryTemplate

• Kept the existing inline email fields intact for backward compatibility • Added validation so an email template is either: • inline content (

subject

+

html_template

), or • a provider template (

provider_template

) • Regenerated checked-in generated artifacts This preserves existing inline-email behavior while allowing providers to use externally managed templates with dynamic data. How was this patch tested? This change was tested by: • running

buf lint --path flyteidl2/notification/definition.proto

• regenerating the checked-in artifacts and verifying the generated outputs Labels

changed

Setup process No special setup required beyond the normal protobuf generation workflow. Screenshots N/A Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. Related PRs N/A Docs link N/A flyteorg/flyte