The template resource does most of that work inside the provider at compile-time. The resource is used to validate that your arguments to the resource are valid, its not until you get into define_resource_requirements inside of the provider that you would throw the EnclosingDirectoryDoesNotExist exception. As far as I can tell the example Chris gives should work, so we probably need the real code and the real output showing the actual exception, plus the backtrace. Offhand I'd suspect something more like a simple "/opt/some_path/conf" vs. "/opt/some-path/conf" typo but there's not enough information to say. However, I would have expected either an EnclosingDirectoryDoesNotExist or the error message about the source of the template not being found for the simple "file not found" cases that I can think of. If chef is spitting back a stock "No such file or directory" then I'm not sure what code path is getting hit without the text of the exception and ideally the backtrace. On 11/13/14, 12:46 PM, Ranjib Dey wrote: " type="cite"> |
Archive powered by MHonArc 2.6.16.