because the parameters specified for the library (or the files those
parameters point to) may have changed.
-Since Kea-2.7.6, the server is able to load hook libraries specifying only the binary name,
-if they reside in the default installation directory (the path is OS specific).
-The default hook libraries installation path is provided in the config report as
-"Hooks directory".
+As of Kea 2.7.8, hook libriares may only be loaded from the default installation
+directory which is provided in the config report as "Hooks directory". If a path
+other than the default installation directory is specified Kea will emit an error
+and refuse to load the library. For ease of use the path may simply be omitted.
.. code-block:: json
}
}
+
Libraries may have additional parameters that are not mandatory, in the
sense that there may be libraries that do not require them. However, for any
given library there is often a requirement to specify a certain
EXPECT_FALSE(unparked);
}
+// Verifies HooksParser::validatePath() when enforce_path is true.
TEST(HooksParser, validatePathEnforcePath) {
std::string def_path(HooksLibrariesParser::default_hooks_path_);
struct Scenario {
}
}
+// Verifies HooksParser::validatePath() when enforce_path is false.
TEST(HooksParser, validatePathEnforcePathFalse) {
std::string def_path(HooksLibrariesParser::default_hooks_path_);
struct Scenario {
}
+
+// Verifies FileManager::validatePath() when enforce_path is true.
TEST(FileManager, validatePathEnforcePath) {
std::string def_path(TEST_DATA_BUILDDIR);
struct Scenario {
}
}
+// Verifies FileManager::validatePath() when enforce_path is false.
TEST(FileManager, validatePathEnforcePathFalse) {
std::string def_path(TEST_DATA_BUILDDIR);
struct Scenario {
}
}
-
} // namespace