Before
An operator likely created the project and each infrastructure asset separately, moving between account, networking, compute, and identity operations. They also had to wait for each action to complete before starting the next one and perform the final group-membership update manually.
How it works
- Receive the triggering email event and create the cloud project, then provision its private network.
- Create the security group and server in sequence, proceeding only after the preceding infrastructure action completes.
- Add the application user to a group to finish the access-configuration stage; the workflow stops if any step fails.
Workflow details
- Trigger and sequencing: The workflow starts when an emailhook event is received and runs the provisioning actions in a fixed sequence. Each stage is linked to the successful completion of the previous stage, and execution stops when an individual action fails.
- Project foundation: The workflow first creates a cloud project, then creates a private network in the fr-par-1 zone. This establishes the project and its core networking resource before compute infrastructure is provisioned.
- Network security: After the private network is created, the workflow creates a security group in the same zone with the configured acceptance settings. This prepares the security configuration required for the server stage.
- Compute provisioning: The workflow then creates a server in the fr-par-1 zone using the configured local setting, following the completed security-group setup.
- Access configuration: Once the server is created, the workflow adds an application user to a group, completing the defined project and asset configuration sequence without requiring a separate manual handoff between stages.
What changed
The complete five-action setup sequence now runs automatically in a defined order from one trigger. Dependencies are handled by the workflow, and a failure stops the sequence instead of allowing later configuration actions to run without the required preceding asset.
Work removed
Manually creating the project, private network, security group, and server one by one; waiting between dependent provisioning actions; and manually adding an application user to a group.
Expected outcome
Each successful run can cover up to five recurring provisioning and access-configuration actions without separate manual handoffs.
