leehaut opened a new pull request, #8097: URL: https://github.com/apache/hop/pull/8097
Fix https://github.com/apache/hop/issues/8096 ## Summary - When a pipeline is executed remotely with **Export linked resources to server**, `#{variable-resolver:...}` expressions were resolved against the Hop Server process-global metadata (`config/projects/default/metadata`) instead of the metadata bundled in the export ZIP. - `Variables` already loaded the Variable Resolver from the current execution metadata, but `VariableResolverPipeline.resolve()` then called `HopMetadataInstance.getMetadataProvider()` to look up the referenced run configuration and pipeline. That lookup failed with `Unable to find the specified pipeline run configuration '...' in metadata provider: ... config/projects/default/metadata`. - Use `IVariables.findExecutionMetadataProvider()` (walk the parent variable space to the running pipeline/workflow) and fall back to the process-global provider only when none is set. Local runs keep using the open project metadata. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
