You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my_role I use rvm1_default_ruby_version value to configure apache. I expect it is ruby-2.1.1, but actually it is set to ruby-2.3.5.
I factored tests app to reproduce the issue and print rvm1_default_ruby_version before, inside and after my role. It prints ruby-2.1.1, ruby-2.3.5 and ruby-2.1.1. I expect it is ruby-2.1.1.
TL;DR; inside my role rvm1_default_ruby_version does not equal to value set in inventory file.
The text was updated successfully, but these errors were encountered:
bolshakov
changed the title
Latest value from rvm1_rubies even if rvm1_default_ruby_version is set
Lost value from rvm1_rubies even if rvm1_default_ruby_version is set
Jan 15, 2018
bolshakov
changed the title
Lost value from rvm1_rubies even if rvm1_default_ruby_version is set
Last value from rvm1_rubies even if rvm1_default_ruby_version is set
Jan 15, 2018
Inventory file:
My playbook looks like this:
In
my_role
I uservm1_default_ruby_version
value to configure apache. I expect it isruby-2.1.1
, but actually it is set toruby-2.3.5
.I factored tests app to reproduce the issue and print
rvm1_default_ruby_version
before, inside and after my role. It printsruby-2.1.1
,ruby-2.3.5
andruby-2.1.1
. I expect it isruby-2.1.1
.TL;DR; inside my role
rvm1_default_ruby_version
does not equal to value set in inventory file.Possibly related issue #34
The text was updated successfully, but these errors were encountered: