3 Commits (88c4b644005c5f674e9d03abae7e1cccda4fd23e)

Author	SHA1	Message	Date
Patrick Ohly	bf08f5c63c	e2e: allow unknown providers with a warning ... The E2E refactoring tightened the sanity checking of the --provider parameter such that it only allowed known providers. That seemed to make sense because it catches typos, but it turned out that various callers depended on the "accept arbitrary provider value" behavior, therefore it gets restored.	2018-10-24 21:57:02 +02:00
Benjamin Elder	3787a4b5be	register skeleton provider	2018-10-19 17:05:06 -07:00
Patrick Ohly	8b17db7e0c	e2e: modular framework ... Not all users of the E2E framework want to run cloud-provider specific tests. By splitting out the code it becomes possible to decide in a E2E test suite which providers are supported. This is achieved in two ways: - the framework calls certain functions through a provider interface instead of calling specific cloud provider functions directly - tests that are cloud-provider specific directly import the new provider packages The ingress test utilities are only needed by a few tests. Splitting them out into a separate package makes the framework simpler for test suites not using those tests. Fixes: #66649	2018-10-11 11:16:11 +02:00