We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Entity Mailer should be used for all business ops (current entity & namex)
Entity Mailer should move to using cloud event messages (currently namex)
Entity Mailer should track incoming messages and ones completed so that they get processed only 1x to completion.
Entity Mailer should propagate the CTX values and identifier in cloud-event to other systems, logs and history storage.
At least part of the work for this ticket is being covered in this bug fix: https://app.zenhub.com/workspaces/entity-5bf2f2164b5806bc2bf60531/issues/bcgov/entity/7882
The text was updated successfully, but these errors were encountered:
This is likely about a day or two worth of work.
Sorry, something went wrong.
thorwolpert
lmcclung
No branches or pull requests
Entity Mailer should be used for all business ops (current entity & namex)
Entity Mailer should move to using cloud event messages (currently namex)
Entity Mailer should track incoming messages and ones completed so that they get processed only 1x to completion.
Entity Mailer should propagate the CTX values and identifier in cloud-event to other systems, logs and history storage.
At least part of the work for this ticket is being covered in this bug fix: https://app.zenhub.com/workspaces/entity-5bf2f2164b5806bc2bf60531/issues/bcgov/entity/7882
The text was updated successfully, but these errors were encountered: