Offboarding - clean up email references

[tiffanychu90]

Description

Describe your changes and why you're making them. Please include the context, motivation, and relevant dependencies.

Resolves #3370

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation
• Other - clean up email references for former contractors. No longer need email alerts ct-bdat-internal Slack thread

How has this been tested?

Post-merge follow-ups

Document any actions that must be taken post-merge to deploy or otherwise implement the changes in this PR (for example, running a full refresh of some incremental model in dbt). If these actions will take more than a few hours after the merge or if they will be completed by someone other than the PR author, please create a dedicated follow-up issue and link it here to track resolution.

• No action required
• Actions required (specified below)

[github-actions]

The following changes will be applied to the production Kubernetes cluster upon merge.

BE AWARE this may not reveal changes that have been manually applied to the cluster getting undone—applying manual changes to the cluster should be avoided.

No manifest changes found for prod.

[tiffanychu90]

@evansiroky: can I remove this DAG completely because everyone in the email list is getting removed? Instead of an if/else to print a log, I can remove the entire DAG. Do I need to update anything else so I don't break Airflow?

[tiffanychu90]

The following changes will be applied to the production Kubernetes cluster upon merge.

BE AWARE this may not reveal changes that have been manually applied to the cluster getting undone—applying manual changes to the cluster should be avoided.

No manifest changes found for prod.

@vevetron: Which change did I make to do this? How do I not kill Kubernetes cluster?

[vevetron]

@evansiroky: can I remove this DAG completely because everyone in the email list is getting removed? Instead of an if/else to print a log, I can remove the entire DAG. Do I need to update anything else so I don't break Airflow?

I think it might be worth keeping the dag for possible future development.

[vevetron]

LGTM

[vevetron]

The following changes will be applied to the production Kubernetes cluster upon merge.
BE AWARE this may not reveal changes that have been manually applied to the cluster getting undone—applying manual changes to the cluster should be avoided.
No manifest changes found for prod.

@vevetron: Which change did I make to do this? How do I not kill Kubernetes cluster?

I'm not sure why this came up, I think everything is fine. Nobody is making manual changes to the kubernetes cluster as far as I know.

[github-actions]

The following changes will be applied to the production Kubernetes cluster upon merge.

BE AWARE this may not reveal changes that have been manually applied to the cluster getting undone—applying manual changes to the cluster should be avoided.

No manifest changes found for prod.