Dave
Dave
How does removing secrets make backup useless? Manually configuring 1 line/5 lines in a disaster recovery situation vs 1000 lines makes it useless?
One option (not solution for your problem): If im not mistaken you can increase the time to daily or weekly to mitigate the diff count.
@waid I was able to do exactly what you are trying but using the hooks section. Hope it's useful https://github.com/ytti/oxidized/issues/396
@wiad yes i was looking to try it since this will probably be a more elegant solution than the hooks method. will probably have an answer by next week though....
I thought i had replied. Well either way it seems there was a git bug with v0.14.2. Now running v0.14.3. I made the changes to the node{s}.rb and worker.rb files....
@wiad That was the issue. Would it be possible to control how git is initialized? i.e: With these changes the outputs looks like this, which is expected: > ~/repository/GroupA/subgroup{a,b,c}/node{a,b,c}/node{a,b,c}_flat_file >...
Yeah i thought that too. I guess this can be closed. Thanks!
@wiad I was about to ask that question. Thank you @ytti
What have been doing for a long time: ``` hooks: first_hook: type: exec events: [post_store] cmd: 'echo "$OX_NODE_NAME commit" > /home/config/oxidized/$OX_NODE_GROUP.git/description' timeout: 10 second_hook: type: exec events: [post_store] cmd: 'mkdir...
Not sure how your source file is setup but we group our nodes. perhaps you are not using groups? In which case you would have to update the cmd accordingly