CAF::FileStatus about caf HOT 8 CLOSED

I think Perl built in functions can be mocked almost as easily as a module function, but the real benefit of a CAF wrapper is that the component author does not have to think about NoAction support -- it's just part of the library.

from caf.

It was my point in fact! Provide an API that handles mocking transparently for the component author, without any specific code, variable or whatever. I imagine that most of the things I mentioned will be very simple in term of implementation.

from caf.

This is unlikely to happen in the 14.12 cycle...

from caf.

Or the 15.4 cycle...

from caf.

Or the 15.6 cycle...

from caf.

@ned21 you can't mock the perl builtins -f etc. Other nice thing would be integration with Test::Quattor, so when you fake the contents of a file with set_file_contents, a file existence test should report this fake file as being present (and the whole subtree should be testable as exsting directories).

i'm willing to do some effort here, but i need something more than just filestatus, i need some basics like

• LC::Check::_unlink with directory support
• existence checks for directory (-d), file (-f || -l) or anything (-e || -l)
• mkdir (also for mocking)

this can all go in one module imho, but it will need a better name. or more than one module.
i would also need some advise how reporting would be handled (do we throw errors? log errors? store error message in some magic exported variable?)

from caf.

see also

• quattor/configuration-modules-core#648
• work done in https://github.com/quattor/configuration-modules-core/pull/615/files#diff-03b83223101921d4405f8416363c3a20R359

from caf.

Closing this issue after #142 and #255.

from caf.