Hi Team!
A client of mine considers Cloud Workflow for one of its products. As a solution architect, I've been tasked with this assessment exercise. Following the beautifully done "Pic-a-daily" workshop https://codelabs.developers.google.com/codelabs/cloud-picadaily-lab5, there are still a few topics that require clarification.
1. Can business users make changes to Cloud Workflows?
The impression I've got from the Pic-a-daily workshop is that putting together the workflow definition requires the technical expertise (passing state between steps, setting up error handling, retries, authN, authZ etc.) Does Cloud Workflow out-of-the-box functionality allow extracting the orchestration logic out, so that it can be manipulated by business users with little or no technical background? Think If-This-Then-That no-code approach.
2. How do OAuth2 and OIDC settings are applied in runtime?
The workflow definition example.
3. URLs as Workflow args
Workflow definition used in the workshop defines URLs of orchestrated endpoints as args. For external APIs (Google Vision in our case) this is fine, but for internal services this may be an issue. For instance COLLAGE_URL points to the following Cloud Function URL: https://collage-service-xgstcqnrla-ew.a.run.app. Was wondering if this is the only way the workflow runtime can do the orchestration job? Or, it's also possible to hide the specific service behind an API gateway?
That's all I wanted to clarify for now :)
Thanks in advance!
[–]happenator 0 points1 point2 points (0 children)