Before
An operator likely had to identify the requested project, verify that the requester was authorized, retrieve the project's owner information, and coordinate confirmation manually. They then had to switch between cloud administration tools and team messaging to perform or cancel the deletion and communicate the result.
How it works
- Validate the incoming requester and retrieve the specified project together with its IAM owner information.
- Send the project details to Slack and wait for an explicit Yes or No confirmation.
- For an authorized approval, authenticate and submit the project for deletion; otherwise, stop the process and notify the channel.
Workflow details
- Request validation: An incoming email-triggered request starts the workflow, which checks whether the requester is included in the authorized user list before continuing.
- Project and ownership review: The workflow retrieves the specified cloud project and its IAM policy to identify the project owner. It then sends the project number, project ID, and owner information to a Slack channel for review.
- Human confirmation: The process pauses for a Yes or No response in Slack. A negative response stops the deletion path and posts an abortion notice, preserving a clear record that the project was not submitted for deletion.
- Controlled execution: When confirmation is received from an authorized requester, the workflow prepares an impersonated identity, generates the required authentication credentials, and submits the targeted project for deletion.
- Completion notification: After submission, the workflow posts a completion message to the same Slack conversation, making the action status available to the team without requiring a separate follow-up.
What changed
Project deletion requests now move from an incoming email to authorization, ownership review, Slack confirmation, and controlled submission through one workflow. The human decision remains the explicit Yes or No approval in Slack, while the surrounding checks, authentication preparation, execution, and status notifications happen automatically.
Work removed
Manually checking the requester against an authorized-user list, looking up the project and its IAM owner, copying project details into a confirmation message, waiting for and interpreting the approval response, preparing deletion credentials, submitting the project for deletion, and posting completion or cancellation notices.
Expected outcome
A confirmed request can remove roughly 5 to 7 recurring manual actions while ensuring that only authorized, explicitly approved projects are submitted for deletion.
