Onur Filiz a35f8ae914 invoke: Enable plugin file names with extensions ... A CNI network configuration file contains the plugin's executable file name. Some platforms like Windows require a file name extension for executables. This causes unnecessary burden on admins as they now have to maintain two versions of each type of netconfig file, which differ only by the ".exe" extension. A much simpler design is for invoke package to also look for well-known extensions on platforms that require it. Existing tests are improved and new tests are added to cover the new behavior. Fixes #360		2017-02-04 12:01:47 -08:00
..
fakes	pkg/invoke: refactor plugin exec and backfill unit tests	2016-09-02 15:59:25 -04:00
args.go	all: assert internal objects implement interfaces	2016-12-14 17:09:01 -06:00
delegate.go	types: make Result an interface and move existing Result to separate package	2017-01-25 11:31:18 -06:00
exec_test.go	spec/plugins: return interface details and multiple IP addresses to runtime	2017-01-25 11:31:18 -06:00
exec.go	types: make Result an interface and move existing Result to separate package	2017-01-25 11:31:18 -06:00
find_test.go	invoke: Enable plugin file names with extensions	2017-02-04 12:01:47 -08:00
find.go	invoke: Enable plugin file names with extensions	2017-02-04 12:01:47 -08:00
get_version_integration_test.go	versioning: revert spec version to 0.2.0	2016-09-06 15:37:42 -04:00
invoke_suite_test.go	invoke: backfill tests for plugin execution	2016-08-30 23:52:47 -04:00
os_unix.go	invoke: Enable plugin file names with extensions	2017-02-04 12:01:47 -08:00
os_windows.go	invoke: Enable plugin file names with extensions	2017-02-04 12:01:47 -08:00
raw_exec_test.go	spec/plugins: return interface details and multiple IP addresses to runtime	2017-01-25 11:31:18 -06:00
raw_exec.go	pkg/invoke: refactor plugin exec and backfill unit tests	2016-09-02 15:59:25 -04:00