You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The structure of the SNS payloads seems to vary quite a bit for the various statuses. I've been able to find everything I need for the most part, except for the content of the comment field when an access request is rejected. The event payload from the "approved" status contains a "lastTaskResult" key which I can mine for the comment, but that key is not present in the payload for the rejected event.
Any chance we could get these comments stored at the top-level of the event payload? Or just include the lastTaskResult key in all of the status payloads? Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The structure of the SNS payloads seems to vary quite a bit for the various statuses. I've been able to find everything I need for the most part, except for the content of the comment field when an access request is rejected. The event payload from the "approved" status contains a "lastTaskResult" key which I can mine for the comment, but that key is not present in the payload for the rejected event.
Any chance we could get these comments stored at the top-level of the event payload? Or just include the lastTaskResult key in all of the status payloads? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions