This repository has been archived by the owner on Sep 24, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
Ralsh not picking up providers automatically #34
Comments
garethr
added a commit
to garethr/libral
that referenced
this issue
Jun 23, 2017
I put this together for my own purposes but sharing here as it's likely useful for others. A couple of related thoughts: * I'll update the docs with instructions for mounting providers for testing once puppetlabs-toy-chest#34 is resolved. * I could have used the new multi-state builds to avoid some of the apt wranging, but left this way for now until multi-stage builds works it's way into a stable Docker release * This only supports building from the precompiled binary. I'll take a run at converting the HACKING instructions at some point so you can build using Docker, that should be a separate PR I also haven't pushed an image to Docker Hub. I would be happy to do that if useful or hold off for now.
There's a few things going on here:
I'll have to think about how to make the shell script wrapper behave more like what the docs say; e.g., by transforming an existing |
lutter
pushed a commit
that referenced
this issue
Jun 26, 2017
I put this together for my own purposes but sharing here as it's likely useful for others. A couple of related thoughts: * I'll update the docs with instructions for mounting providers for testing once #34 is resolved. * I could have used the new multi-state builds to avoid some of the apt wranging, but left this way for now until multi-stage builds works it's way into a stable Docker release * This only supports building from the precompiled binary. I'll take a run at converting the HACKING instructions at some point so you can build using Docker, that should be a separate PR I also haven't pushed an image to Docker Hub. I would be happy to do that if useful or hold off for now.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
According to the readme providers should be discovered either via the ENV, a flag or from a known directory. From some basic testing this doesn't appear to be the case?
(Note this testing was done in a Docker container running ubuntu:latest)
I have the example providers available:
If we try and load them using the ENV they are not picked up.
If we assume they should be picked up because they are in the default directory from the README they are also not picked up.
But if we use
--include
they are picked up. Note the python provider warning and the mruby provider being loaded.Based on the README I would have expected the same output for all of these commands.
The text was updated successfully, but these errors were encountered: