[iennae]

Description

Callers that trigger workflows asynchronously or inspect past runs need to fetch execution state and output by execution ID.

Adds get_execution.py (workflows_get_execution) using executions_v1.ExecutionsClient.get_execution, with unit and gated live integration tests.

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/get_execution.py:15, tag workflows_get_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 get_execution.py and its corresponding tests to retrieve Google Cloud Workflows execution details. The feedback suggests using the client library's built-in execution_path helper method instead of manual string formatting, mocking this method in the unit tests, and conditionally printing the Result and Error fields to prevent confusing output when they are empty.

[gemini-code-assist]

Use the client library's built-in execution_path helper method to construct the resource name instead of manual string formatting. This is more robust, idiomatic, and prevents potential formatting errors.

    name = client.execution_path(
        project=project_id,
        location=location_id,
        workflow=workflow_id,
        execution=execution_id,
    )

[gemini-code-assist]

Conditionally print the Result and Error fields only when they are populated. Printing empty/unset fields (e.g., printing Error: for a successful execution or Result: for a failed execution) can be confusing to users running the sample.

Suggested change

	print(f"Resource ID: {execution.name}")
	# The result is set when the execution succeeds; the error when it fails.
	print(f"Error: {execution.error.payload}")
	print(f"Result: {execution.result}")
	print(f"State: {execution.state.name}")
	print(f"Resource ID: {execution.name}")
	print(f"State: {execution.state.name}")
	if execution.result:
	print(f"Result: {execution.result}")
	if execution.error and execution.error.payload:
	print(f"Error: {execution.error.payload}")

[gemini-code-assist]

Mock the execution_path method on the client to return the expected execution name. This ensures the unit test remains correct and passes when using the client's built-in path helper.

Suggested change

	client = mock_client_class.return_value
	client.get_execution.return_value = executions_v1.Execution(
	name=EXECUTION_NAME,
	state=executions_v1.Execution.State.SUCCEEDED,
	result='"done"',
	)
	client = mock_client_class.return_value
	client.execution_path.return_value = EXECUTION_NAME
	client.get_execution.return_value = executions_v1.Execution(
	name=EXECUTION_NAME,
	state=executions_v1.Execution.State.SUCCEEDED,
	result='"done"',
	)