feat(wandb): store Flyte execution ID in wandb run config for reverse lookups

[ben-chen]

Why are the changes needed?

Currently there is no way to look up the corresponding Flyte execution from a W&B run. The reverse direction (Flyte → W&B) is also not straightforward. By storing the Flyte execution ID in the W&B run config, we enable a single-lookup mapping in either direction — given a W&B run, you can directly find the Flyte execution.

What changes were proposed in this pull request?

After wandb.init() in remote execution, stores three keys in the wandb run config:

• flyte_execution_id — the execution name
• flyte_execution_project — the Flyte project
• flyte_execution_domain — the Flyte domain

These are only set during remote (non-local) execution. allow_val_change=True is passed to avoid conflicts if wandb config was already initialized with defaults.

How was this patch tested?

Updated the existing test_non_local_execution test to mock execution_id.project and execution_id.domain, and added an assertion that run.config.update is called with the expected Flyte metadata.

Note for reviewers: The test_secret_callable_remote test also exercises the remote execution path but does not explicitly assert the config update. It should still pass since Mock() auto-creates attributes, but the config update call is not verified there.

Human Review Checklist

• Verify allow_val_change=True is the right approach (vs. setting config keys before wandb.init)
• Confirm the key names (flyte_execution_id, flyte_execution_project, flyte_execution_domain) match what downstream consumers (e.g. Overseer dashboard) will query
• Check CI passes — local tests could not be run due to environment constraints

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

---

Link to Devin Session: https://app.devin.ai/sessions/71ca8c0e52c647fcaf3aeeac880073f9
Requested by: @ben-chen

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.