Joe Bryan

I suspect %ames is more likely to have an issue with this than %jael. The `:dns` app also might need some adjustment for this case. Happy to take a look...

I was going to suggest `./ml info`, but that has a return code of 0 whether the environment exists or not. Sounds like both of those commands need updates.

This functionality would be a superset of the proposal in #133.

thanks @grtjn, I opened joemfb/mlpm#1 to track the possibility of config fragments in packages.

re: your earlier comments, order is import for REST extensions/transforms, which are parsed and validated when deployed. To be safe, the deployer needs a reverse topological sort of modules and...

Finally, here's are the deployment notes that I originally promised... I apologize for both the delay, and the length, but there's a lot to consider here. I'd appreciate any feedback...

This confusion is my fault: I confused @grtjn's comment re: the Roxy bootstrap module location support with MarkLogic's general capability. The gist I linked earlier (the "crude" deployment mechanism for...

That's the approach taken by the linked gist, and it should be sufficient for most use-cases. However REST extensions/transformations are library modules, and could be imported by other modules (although...

see the README for an `app_specific.rb` snippet that does just that: https://github.com/joemfb/mlpm. However, that kind of run-time dependency on the `mlpm` client might not be preferable long term ...

Shouldn't need to prompt: the credentials used for module deployment are sufficient. Not sure about tighter integration, I don't think you want to deploy packages every time you deploy modules....