<div dir="ltr">Hello All,<div>Current implementation of <span class="" id=":6lw.1" tabindex="-1" style="background:yellow"><span class="" id=":6lw.1" tabindex="-1">plugins</span></span> in Fuel unpacks <span class="" id=":6lw.2" tabindex="-1" style="background:yellow"><span class="" id=":6lw.2" tabindex="-1">plugin</span></span> tarball into /var/www/<span class="" id=":6lw.3" tabindex="-1" style="background:yellow"><span class="" id=":6lw.3" tabindex="-1">nailgun</span></span>/<span class="" id=":6lw.4" tabindex="-1" style="background:yellow"><span class="" id=":6lw.4" tabindex="-1">plugins</span></span>/.</div><div>If we implement deployment part of <span class="" id=":6lw.5" tabindex="-1" style="background:yellow"><span class="" id=":6lw.5" tabindex="-1">plugin</span></span> using puppet there is a setting </div><div>puppet_modules:</div><div><br></div><div>This setting should specify path to modules folder. As soon as main deployment part of <span class="" id=":6lw.6" tabindex="-1" style="background:yellow"><span class="" id=":6lw.6" tabindex="-1">plugin</span></span> is implemented as a Puppet module module path setting should be:</div><div><br></div><div>puppet_modules: puppet/</div><div><br></div><div>There is big probability that <span class="" id=":6lw.7" tabindex="-1" style="background:yellow"><span class="" id=":6lw.7" tabindex="-1">plugin</span></span> implementation will require some custom resources and functions which are implemented in fuel-library (e.g. service <span class="" id=":6lw.8" tabindex="-1" style="background:yellow"><span class="" id=":6lw.8" tabindex="-1">config</span></span> resources, <span class="" id=":6lw.10" tabindex="-1" style="background:yellow"><span class="" id=":6lw.9" tabindex="-1">stdlib</span></span> functions e.t.c). So in order to use them <span class="" id=":6lw.11" tabindex="-1" style="background:yellow"><span class="" id=":6lw.10" tabindex="-1">plugin</span></span> developer has to copy them from fuel-library into <span class="" id=":6lw.12" tabindex="-1" style="background:yellow"><span class="" id=":6lw.11" tabindex="-1">plugin</span></span> (if <span class="" id=":6lw.13" tabindex="-1" style="background:yellow"><span class="" id=":6lw.12" tabindex="-1">i'm</span></span> not missing something). This is not really convenient from my perspective.</div><div><br></div><div>I'd like to suggest to treat puppet_modules parameter as an array and pass it to puppet binary as</div><div># puppet apply --<span class="" id=":6lw.14" tabindex="-1" style="background:yellow"><span class="" id=":6lw.13" tabindex="-1">modulepath</span></span>=<modulepath1>:<modulepath2></div><div>This will allow to add /etc/puppet/modules as module path and use resources and functions form fuel-library.</div><div><br></div><div>P.S.:</div><div>puppet_modules: "puppet/:/etc/puppet/<span class="" id=":6lw.14" tabindex="-1">moules</span>/: <- is not allowed by <span class="" id=":6lw.15" tabindex="-1">yaml</span> parser (and <span class="" id=":6lw.16" tabindex="-1">yaml</span> format I believe)<br></div><div><br></div><div>Any suggestions here?</div><div><div><br></div><div><br></div>-- <br><div class="gmail_signature">Kind regards<div><span class="" id=":6lw.15" tabindex="-1" style="background:yellow"><span class="" id=":6lw.18" tabindex="-1">Dmitry</span></span> <span class="" id=":6lw.16" tabindex="-1" style="background:yellow"><span class="" id=":6lw.19" tabindex="-1">Ukov</span></span></div><div>IT Engineer</div><div><div><span class="" id=":6lw.17" tabindex="-1" style="background:yellow"><span class="" id=":6lw.20" tabindex="-1">Mirantis</span></span>, Inc.</div></div><div><br></div></div>
</div></div>