LPETIT458 commented on issue #8106: URL: https://github.com/apache/hop/issues/8106#issuecomment-5510108121
Does this limitation also apply when the S3 connection metadata is shared via NFS between Hop GUI and Hop Server (i.e. same NFS mount, same metadata path, on both sides)? In our setup the connection definition itself isn't transmitted as part of a resource bundle — it's already present locally on the server through the shared NFS mount, using the exact same path as on the client. We'd expect the server to resolve it from its own local metadata in that case, but we're still seeing the connection name substituted literally instead of being resolved. -- 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]
