First, we begin by installing a new instance of Killbill and Kaui. We have
tried these combinations:
* Killbill 0.18.2 + Kaui 0.8.1
* Killbill 0.18.6 + Kaui 0.8.7
We then immediately create the new tenant with:
curl -v \
-X POST \
-u admin:password \
-H 'Content-Type: application/json' \
-H 'X-Killbill-CreatedBy: admin' \
-d '{"apiKey": "bob", "apiSecret": "lazar"}' \
"
http://127.0.0.1:8080/1.0/kb/tenants"
This new tenant automatically has a sample catalog available (which is
great!) but we want to override it with a new one. So we navigate to
Catalog > Existing Plans > Enable Advanced Configuration (Upload XML) and
attempt to upload a different catalog. This results in "Error while
communicating with the Kill Bill server: Error 400: Invalid catalog for
tenant : 1". (Note: The catalog XML was validated with
killbill-catalog-0.18.X-load-tool.jar and was somehow successfully
uploaded in the past, so it is known to work.)
Since there are no subscriptions or invoices yet, we then try to remove
all catalog data from the database to start fresh, using this command:
echo "use killbill; delete from tenant_kvs;" | docker exec -i db mysql
-h localhost -uroot -proot
However, this does not help -- the same error above is returned when the
catalog XML is uploaded. Other posts mention clearing the cache, but do
not indicate how to do so. What steps are we missing?
And as a follow-up question: If future changes to the catalog are needed,
how would they be uploaded since this error seems to always be the result
if one already exists?
Thanks for any insight.