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/python/setup.py b/python/setup.py
index 2166e66..b82b424 100644
--- a/python/setup.py
+++ b/python/setup.py
@@ -12,6 +12,7 @@
'api/*.py',
'api/software/*.py',
'api/software/**/*.py',
+ 'payload/*.py',
'test/*.py',
'test/fake_program/*',
'test/fake_project/*',