Unknown dependency conform for environment dev

[bitwalker]

Unknown dependency conform for environment dev

[bitwalker]

Very odd, there's been some churn to the way umbrella projects work in Elixir as of late, so I'm guessing this is a bug with the way exrm handles umbrellas not having been updated to reflect those changes. I may not get to this tonight yet, but I'll for sure address sometime tomorrow.

Just for extra background, conform is indeed an internal dependency of exrm, and is used solely for handling the .conf file in production. It also generates the .schema.exs and .conf if one is not present, but beyond that it doesn't do anything until the release is booted, at which point it merges config settings it contains over the top of the existing sys.config file for the release. This is so you can expose a friendly config to sysadmins, and make sure that those config values are validated/transformed to something more useful behind the scenes. There is no requirement that you use the .conf (simply remove any content from the .conf and .schema.exs files), but it's there as a useful convenience. I'll likely extract conform back out of exrm in a future release, and make it an optional plugin which you can install, but I haven't worked out how to handle plugins which also require boot script integration. @alco and I had some ideas, primarily around the concept of sourcing in bash scripts which add functionality. There is a great deal of complexity to sort out around that though, since it has the potential to make troubleshooting release issues significantly more complex. All of this is on my list of future improvements though, so if you have ideas/comments/requests, feel free to voice them.

[bitwalker]

@novabyte This has now been fixed in the latest versions of exrm and conform (0.12.7 and 0.8.3 respectively). I merged your PR for exrm-umbrella-test and used that to validate that things are working again, so please let me know if you run into any new issues. Thanks for the help!

[novabyte]

@bitwalker I'm glad I could help. Next time I'll try to submit the fix for the problem rather than just update the test project that makes it reproduceable. I'm going to test the latest release with my umbrella project and let you know if I encounter any trouble.