[iennae]

Description

Adds cancel_execution.py (workflows_cancel_execution) using executions_v1.ExecutionsClient.cancel_execution to terminate an in-flight execution, verified by unit tests and a gated live integration test against a sleeping workflow.

Note: Stacked on #14797 (refactor/workflows-cloud-client-package) so this PR shows only this sample's diff.

Checklist

Testing

• I have tested this change on a live environment and verified it works as intended. Unit and live integration tests pass on Python 3.13.

Compliance & Style

• I have followed the Sample Guidelines.
• The README is updated with all relevant information (if applicable).
• If this PR adds a new sample directory: I updated the CODEOWNERS file. Not applicable: all changes are inside workflows/cloud-client/.

---

Post-Approval Actions

• Please merge this PR for me once it is approved

[snippet-bot]

Here is the summary of changes.

You are about to add 1 region tag.

• workflows/cloud-client/src/workflows_samples/cancel_execution.py:15, tag workflows_cancel_execution

---

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

• Refresh this comment

[gemini-code-assist]

Code Review

This pull request introduces a new sample script and corresponding tests for cancelling a running Google Cloud Workflows execution. The feedback suggests utilizing the client library's built-in helper methods (execution_path and workflow_path) to construct resource paths instead of manually formatting them with f-strings, which improves robustness and aligns with best practices.

[gemini-code-assist]

Use the client's built-in execution_path helper method instead of manually constructing the resource path with f-strings. This is more robust, less prone to formatting errors, and aligns with Google Cloud client library best practices.

    name = client.execution_path(project_id, location_id, workflow_id, execution_id)

[gemini-code-assist]

Use the client's built-in workflow_path helper method instead of manually constructing the parent resource path with f-strings. This is more robust and consistent with the rest of the codebase.

Suggested change

	parent = (
	f"projects/{conftest.LIVE_PROJECT_ID}/locations/{conftest.LIVE_LOCATION_ID}"
	f"/workflows/{sleep_workflow_id}"
	)
	parent = executions_client.workflow_path(
	conftest.LIVE_PROJECT_ID,
	conftest.LIVE_LOCATION_ID,
	sleep_workflow_id,
	)