When calling karp-cli resource create using an invalid config (e.g. a field that has a missing type), it creates the MySQL table but then fails to create the Elasticsearch index. The resource then has to be manually deleted.
Maybe it should delete the resource if the create fails? Alternatively, we could validate the resource config first.
When calling
karp-cli resource createusing an invalid config (e.g. a field that has a missing type), it creates the MySQL table but then fails to create the Elasticsearch index. The resource then has to be manually deleted.Maybe it should delete the resource if the create fails? Alternatively, we could validate the resource config first.