TL;DR Can a playbook runtime get the secops user logged in?
We’ve got a SecOps Playbook that processes SNOW requests. At the end we either auto-decide - using SNOW API and a service account, or a manual decision has to happen (approve/reject). Now, we want this manual step to happen in Google SecOps rather than SNOW. I can create a multi-choice step for the agents to provide with their decision, but then we need to ensure the SNOW request is being modified (approved) on behalf of their SNOW account. This would be very easy for me to do if somehow the playbook could get the logged in (into Google SecOps) user id/email who performs this manual action. Because then I can pull the SYS_APPROVER_ID from SNOW via API.
