dklawren
commented
3 years ago Hi @dklawren, we'd like to get additional context for the work that's driving this request. Gene asked the websre team to review and we aren't yet familiar with what's being done here, and I'm hoping you can help. Is there an upstream BMO issue, or a document or even just a Slack discussion, that we could review to gain a better understanding of this request?
Sure. Here are the related links that explain what is happening: https://bugzilla.mozilla.org/show_bug.cgi?id=1612286 https://docs.google.com/document/d/1n9u6bQHmAXlDxpY78KTpFpSWIAhLyeyiK74Y4kf-zaE/edit?ts=5e424e27#heading=h.3o1jg7a1uy5s
Also, a warning. This component of the IAM system is not designed to be resilient against transient errors, so we also need to confirm with you that it's acceptable for these RP notifications to be lossy. If you're already familiar with this concern, then that's a very brief confirmation; if not, we should discuss further to be sure this will still meet your needs.
That is fine and mentioned early on. I have a background process that also looks at accounts in BMO that are linked to IAM and will update if necessary periodically. The ping from CIS to BMO helps make the changes happen more quickly.
dkl
floatingatoll
bkochendorfer
Hi @dklawren, we'd like to get additional context for the work that's driving this request. Gene asked the websre team to review and we aren't yet familiar with what's being done here, and I'm hoping you can help. Is there an upstream BMO issue, or a document or even just a Slack discussion, that we could review to gain a better understanding of this request?
Also, a warning. This component of the IAM system is not designed to be resilient against transient errors, so we also need to confirm with you that it's acceptable for these RP notifications to be lossy. If you're already familiar with this concern, then that's a very brief confirmation; if not, we should discuss further to be sure this will still meet your needs.