Decouple API boundaries from packaging
This was an initial coupling oversight that wasn't caught until the go
bindings were generated/used (since python doesn't care).
This should have never been coupled in the first place since
config_bundle is a packaging detail in how we distro the payloads and
doesn't really define the API boundaries.
BUG=chromium:1062830
TEST=None
Change-Id: If43dd40b32de07912ee1a8cedc3726979aa8e740
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/config/+/2129654
Commit-Queue: C Shapiro <shapiroc@chromium.org>
Tested-by: C Shapiro <shapiroc@chromium.org>
Reviewed-by: Andrew Lamb <andrewlamb@chromium.org>
Reviewed-by: David Burger <dburger@chromium.org>
Reviewed-by: Sean McAllister <smcallis@google.com>
Auto-Submit: C Shapiro <shapiroc@chromium.org>
diff --git a/payload_utils/checker/io_utils_test.py b/payload_utils/checker/io_utils_test.py
index d8f00d0..717ff92 100644
--- a/payload_utils/checker/io_utils_test.py
+++ b/payload_utils/checker/io_utils_test.py
@@ -9,7 +9,7 @@
from checker import io_utils
-from bindings.api.config_bundle_pb2 import ConfigBundle
+from bindings.payload.config_bundle_pb2 import ConfigBundle
from bindings.api.program_pb2 import ProgramList, Program