[Workflow Interface] Fix for WorkspaceExport (Issue #1406)

[refai06]

Summary

This PR fixes an issue related with WorkspaceExport(#1406)

Type of Change (Mandatory)

• Bug fix

Description (Mandatory)

Added flow instance name and modified the return statement to include both flow instance name and runtime instance

Testing

Validated below tutorial

• openfl-tutorials/experimental/workflow/1001_Workspace_Creation_from_JupyterNotebook.ipynb

[theakshaypant]

Since this would also affect FLSpec refactor, would the respective PR (#1363 ) cover that?

[scngupta-dsp]

Since this would also affect FLSpec refactor, would the respective PR (#1363 ) cover that?

@theakshaypant : This PR does not affect refactoring in #1363. Could you please elaborate your concern in more detail?

[teoparvanov]

Since this would also affect FLSpec refactor, would the respective PR (#1363 ) cover that?

@theakshaypant : This PR does not affect refactoring in #1363. Could you please elaborate your concern in more detail?

AFAIU, @theakshaypant refers to the fact that the FLSpec will no longer have a _runtime member variable as part of the #1363 refactoring.

Which additionally raises the question why @ishant162 doesn't modify the _find_runtime_instance() method accordingly?

[theakshaypant]

@teoparvanov Precisely! Per my understanding, this line would not work after the refactor since the Flow does not have a runtime associated with it.

[ishant162]

Since this would also affect FLSpec refactor, would the respective PR (#1363 ) cover that?

@theakshaypant : This PR does not affect refactoring in #1363. Could you please elaborate your concern in more detail?

AFAIU, @theakshaypant refers to the fact that the FLSpec will no longer have a _runtime member variable as part of the #1363 refactoring.

Which additionally raises the question why @ishant162 doesn't modify the _find_runtime_instance() method accordingly?

@teoparvanov, @theakshaypant,
The _find_runtime_instance() method supports the Aggregator-based workflow, where _runtime is still in use. Refactoring in #1363 focused on FederatedRuntime and LocalRuntime, with Aggregator workflow changes planned for a follow-up PR

Since the changes in this PR will be overridden by the follow-up PR maybe the issue resolution could wait for the follow-up PR.