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

Notify subscribers of auto publish failure #608

Merged
merged 2 commits into from
Mar 6, 2025

Conversation

br648
Copy link
Contributor

@br648 br648 commented Mar 4, 2025

Checklist

  • Appropriate branch selected (all PRs must first be merged to dev before they can be merged to master)
  • Any modified or new methods or classes have helpful JavaDoc and code is thoroughly commented
  • The description lists all applicable issues this PR seeks to resolve
  • The description lists any configuration setting(s) that differ from the default settings
  • All tests and CI builds passing

Description

Notify subsribers if an auto published feed fails.

FeedVersionController.publishToExternalResource(latestFeedVersion);
LOG.info("Auto-published feed source {} to external resource.", feedSource.id);
} else {
// Notify feed and project subscribed users of failure.
String message = String.format(
Copy link
Contributor

@binh-dam-ibigroup binh-dam-ibigroup Mar 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will result in two email notifications being sent (for fetched feed versions only):

  1. A useful email with the text outlined in this block,
  2. A more generic email that is already being sent, and that reads: "While attempting to process a new feed version for [feed name], an unrecoverable error was encountered. More details: unknown error". I think we can keep the two, although in some future, it will make sense to propagate the error content from this message to the other one. Thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How quickly are MTC expecting an update? I think for now we go with two email notifications.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can keep it at two emails for now and iterate based on their feedback.

@br648 br648 assigned JymDyerIBI and unassigned br648 Mar 6, 2025
Copy link
Contributor

@JymDyerIBI JymDyerIBI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good.

@br648 br648 merged commit ea218d9 into mtc-deploy Mar 6, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants