Jason Frey

See also https://github.com/danielsdeleo/deep_merge/issues/23

No, there's no option for that from what I can tell. We'd need a new option, so this is an enhancement request. That being said, I'm not sure exactly how...

I agree with this one as well, but it will require a major version bump due to a change in signature. We'd also have to come up with new methods...

Backported to `morphy` in commit 1ade723c9633f56fd5a516a17b26e6be83bfd601. ```text commit 1ade723c9633f56fd5a516a17b26e6be83bfd601 Author: Jason Frey Date: Wed Aug 10 09:50:34 2022 -0400 Merge pull request #22047 from agrare/only_run_wait_for_run_async Only wait for ansible-runner pid...

Backported to `morphy` in commit 5fba0463c12b0192c1145b2a66f646ef45aa1176. ```text commit 5fba0463c12b0192c1145b2a66f646ef45aa1176 Author: Adam Grare Date: Wed Aug 10 08:42:51 2022 -0400 Merge pull request #22048 from Fryguy/use_ansible_path Automatically determine the python path...

I think this feature is kind of cool. I could see people using it for dev/test/prod type breakdowns as well, where they want all 3 to appear in the final...

I don't understand why there's an Array for the namespace, unless you're expecting it to nest multiple levels or something? ```diff -Config::Sources::YAMLSource.new("/Users/userguy/repos/scratch/example.yml", ['new-level']) +Config::Sources::YAMLSource.new("/Users/userguy/repos/scratch/example.yml", 'new-level') ```

@cjlarose That's a good point...I completely forgot that add_source can take arbitrary hashes, so yes I agree with you. EDIT: However, will reload! work with that?

In the proposal the namespace is part of the source, so it could be reloaded.

We also use engines in ManageIQ, but our use case is a little different. Basically we use Rails engines as a plugin system, and one of the pluggable things is...