Conversation
kenyon
left a comment
There was a problem hiding this comment.
I don't see how this changes anything. If you are providing a non-undef value to redis::rdb_save_incremental_fsync, then it will render either rdb-save-incremental-fsync yes or rdb-save-incremental-fsync no.
To be sure, you could add a test like
puppet-redis/spec/classes/redis_spec.rb
Lines 1683 to 1691 in e8d71af
rdb_save_incremental_fsync to false and checks that the config files contains rdb-save-incremental-fsync no.
|
I have corrected the Undef: no config file entry, aka "the default" which may have been "no" in the past but is now "yes" I have separately verified that this works as intended on a real-world instance. edit: i clearly do not now how to use rspec properly |
spec/classes/redis_spec.rb
Outdated
| describe 'test rdb-save-incremental-fsync Undef for redis6' do | ||
| let(:params) do | ||
| { | ||
| rdb_save_incremental_fsync: Undef, |
There was a problem hiding this comment.
| rdb_save_incremental_fsync: Undef, | |
| rdb_save_incremental_fsync: nil, |
…ar with its behaviour
|
no matter what i do with the test, when i set: as part of the rspec test, i can't get the test to pass in the Puppet/ruby stages. I don't see any other tests for |
Pull Request (PR) description
minor change to the
redis.confEPP template to make it possible to disablerdb_save_incremental_fsyncThis Pull Request (PR) fixes the following issues
Fixes #494