#10049 fix: inherit env_override variables from parent plugin settings service Pull request opened by ChidiebereNjoku Closes #9298 Summary & Details When a utility plugin utilizes

inherit_from

, child plugins inherit configurations but fail to properly resolve the parent context's default environment variables during validation or initial subprocess invocation. This happens because

PluginSettingsService.__init__

instantiates

self.env_override

strictly using local plugin, project, and environment configs without evaluating the upstream configuration layers accessible via

self.inherited_settings_service

. As a result, commands like

meltano invoke child_plugin

trigger early validation faults (e.g.,

ParsingError

or required configuration blocks throwing missing environment parameter exceptions) despite those variables being cleanly populated on the parent utility declaration. Proposed Changes • Modified

PluginSettingsService.__init__

to check for an active

self.inherited_settings_service

. • Injected the parent settings manager's compiled

env_override

dictionary into the local plugin

env_override

configuration map prior to evaluation. • This ensures parent-defined environment layouts cascade fully down to inherited children utilities, matching expected configuration behaviors. Summary by Sourcery Bug Fixes: • Fix child plugins not receiving parent-defined environment variables in env_override when inherit_from is used, preventing validation and invocation errors. meltano/meltano