puppet_bundler.git, branch master [puppet_bundler] Dont use curly braces in resource reference 2016-04-28T11:49:36+00:00 varac varacanero@zeromail.org 2016-04-28T11:49:36+00:00 bacec3e072649be4ade56f7df8506b46ae9c5166 Puppet future parser will complain otherwise.
Puppet future parser will complain otherwise.
passing install_method => '' to chose the default package provider was a bit 2012-11-29T20:53:15+00:00 Micah Anderson micah@riseup.net 2012-11-29T20:53:15+00:00 b4a4a8434616247156e59b860b47cc6256ead8d1 opaque in manifests, so allow for 'package' to be passed, which makes it more clear how it is being done
opaque in manifests, so allow for 'package' to be passed, which makes it more
clear how it is being done
add some backwards compatibility 2012-11-21T00:19:21+00:00 Micah Anderson micah@riseup.net 2012-11-21T00:19:21+00:00 b91d6abfa931b8ef63594092d841701d3ee23280 update documentation/comments to reflect reality
update documentation/comments to reflect reality
fix $install_method to work properly 2012-11-21T00:08:45+00:00 Micah Anderson micah@riseup.net 2012-11-21T00:08:45+00:00 cef8d7f65cb9f7931625a900b00a53ffb2848f12 unfortunately, if one attempts to set the $install_method to an empty string, puppet complains that you are interning an empty string. If you set it to undef, then the parameterized default will get chosen. To fix this, I replaced the $bundler::params::install_method default class parameter value with 'rvm' (the value that $bundler::params::install_method defaulted to) and then setup a test to determine if the $install_method was set to undef, if so, then we set a second variable ($provider_method) to undef and use that.
unfortunately, if one attempts to set the $install_method to an empty string,
puppet complains that you are interning an empty string. If you set it to undef,
then the parameterized default will get chosen.

To fix this, I replaced the $bundler::params::install_method default class
parameter value with 'rvm' (the value that $bundler::params::install_method
defaulted to) and then setup a test to determine if the $install_method was set
to undef, if so, then we set a second variable ($provider_method) to undef and
use that.
replace $use_rvm with $install_method to enable more flexible installation 2012-11-20T22:36:12+00:00 Micah Anderson micah@riseup.net 2012-11-20T22:36:12+00:00 038f71b44b1937dd1f349386b6af1a162091c3db possibilities The $use_rvm variable was limited to either using rvm or not, so we replace that with $install_method, defaulting to the previous usage If you set $use_rvm it to not use rvm, then the module would just use the gem. This made it so you couldn't install bundler via a package. So the $install_method was added which enabled you to alter how the non-rvm installation was provided. Unfortunately, it was a mistake to have both $use_rvm and $install_method because $use_rvm is 'true' by default, so if you tried to set an install_method, then it wouldn't work because it would just use the rvm method. So in order to install via something other than rvm or gem, you would need to do both use_rvm => false; install_method => <whatever>. Just having the install_method parameter is much cleaner, because it is generic, doesn't require multiple settings when not installing via rvm or gem, and it defaults to what the module was doing before (using rvm by default).
possibilities

The $use_rvm variable was limited to either using rvm or not, so we replace that
with $install_method, defaulting to the previous usage

If you set $use_rvm it to not use rvm, then the module would just use the
gem. This made it so you couldn't install bundler via a package. So the
$install_method was added which enabled you to alter how the non-rvm
installation was provided.

Unfortunately, it was a mistake to have both $use_rvm and $install_method
because $use_rvm is 'true' by default, so if you tried to set an install_method,
then it wouldn't work because it would just use the rvm method. So in order to
install via something other than rvm or gem, you would need to do both use_rvm
=> false; install_method => <whatever>.

Just having the install_method parameter is much cleaner, because it is generic,
doesn't require multiple settings when not installing via rvm or gem, and it
defaults to what the module was doing before (using rvm by default).
update README.md to provide information about different install_method possibilities 2012-11-13T14:45:43+00:00 Micah Anderson micah@riseup.net 2012-11-13T14:45:43+00:00 f7ceb6d84bf692b98148f75be7cc6584a55bf1a3

note in README that Debian is also supported 2012-10-17T19:36:00+00:00 Micah Anderson micah@riseup.net 2012-10-17T19:36:00+00:00 dede41c7a1ba7d56d25db8a7e83a55f4f2a0bd0f

enable other bundler installation possibilities 2012-10-17T19:35:43+00:00 Micah Anderson micah@riseup.net 2012-10-17T19:35:43+00:00 d60f980d4918708531483c134ee7cacd902724aa The way bundler was installed was either via the rvm method, or through gems. This change provides a parameter $install_method that allows for the non-rvm puppet package resource installation method to be passed a different provider than gem, if desired (eg. for package installation)
The way bundler was installed was either via the rvm method, or through gems. This change provides a parameter $install_method
that allows for the non-rvm puppet package resource installation method to be passed a different provider than gem, if desired
(eg. for package installation)
lint module 2012-10-17T19:08:19+00:00 Micah Anderson micah@riseup.net 2012-10-17T19:08:19+00:00 a8b4676955163dc5e4148e6968bc991c390f0333 Run puppet-lint on module, changes were minor, mostly just trailing spaces, and a couple instances of boolean values being quoted.
Run puppet-lint on module, changes were minor, mostly just trailing spaces, and
a couple instances of boolean values being quoted.
fixed bug when running bundler from user other than root 2012-09-12T22:19:11+00:00 Evan Stachowiak evan.stachowiak@gmail.com 2012-09-12T22:19:11+00:00 7d0ae40d42613aac09f16627edd93a4f46ce1582