Add ability to manipulate config passed to subsystems beyond passing a set of refs #33

cap10morgan · 2024-04-16T19:12:40Z

I have a subsystem that needs its config in a different format (in this case a different key name and turning a port number into a full URL), but it seems all you can do w/ subsystems is pass a set of refs. Is there a way to manipulate the config before it gets passed to the subsystem's start fns?

I don't want to modify the subsystem to accept the parent's config ref as-is b/c I'm just using it as a subsystem in an integration test system where I pull in this other system as a library. Treating it as a subsystem there seemed like a good way to couple its lifecycle to the overall test system I'm starting. But outside of integration testing, it's an entirely different component that is run on its own. So I don't want these two system's configs to be tightly coupled by this test integration.

Let me know if subsystems aren't the best approach here, or if there is already a way to do this config manipulation that I'm not seeing.

Thanks!

flyingmachine · 2024-07-08T03:29:17Z

hey hey! It's taken me a while to get to this, sorry about that. Would it be possible to share an example if this is still an issue?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add ability to manipulate config passed to subsystems beyond passing a set of refs #33

Add ability to manipulate config passed to subsystems beyond passing a set of refs #33

Uh oh!

Add ability to manipulate config passed to subsystems beyond passing a set of refs #33

Add ability to manipulate config passed to subsystems beyond passing a set of refs #33

Comments

Uh oh!