Open ffeldhaus opened 1 year ago
google_cloudfunctions_function.https_trigger_url
maps to a specific API field: https://cloud.google.com/functions/docs/reference/rest/v1/projects.locations.functions#HttpsTrigger Though I'm not sure whether the format is predictable or not.
Based on the linked docs it sounds like the workflow url is entirely predictable: https://workflowexecutions.googleapis.com/v1/projects/PROJECT_NUMBER/locations/LOCATION/workflows/WORKFLOW_NAME/executions
. This could be built using string interpolation - for example:
"https://workflowexecutions.googleapis.com/v1/${google_workflows_workflow.my_workflow.id}/executions"
I'm marking this as a feature request since it could be implemented on the API side and/or the client side, and does not represent a coverage gap compared to the API.
Is there any particular reason that a field would be more useful than doing string interpolation?
+1 to melinath's comment that the url to execute a workflow is always the same, whereas for cloud functions, the url to trigger the function call might be different.
Could you let us know the specific use case that a https_trigger_url
attribute will be useful? Thank you!
Affected Resource(s)
Google Cloud Workflows are usually invoked via the workflow execution URI, e.g. via Cloud Scheduler (see #8832 for an example).
Please add an attribute
https_trigger_url
togoogle_workflows_workflow
similar to thehttps_trigger_url
attribute ingoogle_cloudfunctions_function
.b/321386065