The ESXi configstorecli was introduced back in vSphere 7.0 Update 1 and provides access to the ESXi ConfigStore which responsible for centrally managing all configurations for an ESXi host instead of relying on different methods including a variety of configuration files, I highly recommend reviewing this refresher article HERE if you have not heard of the configstorecli before. The ESXi ConfigStore is also the underlying infrastructure that powers the new vSphere Configuration Profile feature which is also part of the vSphere Lifecycle Manager (vLCM) solution.
For those who currently or plan to automate ESXi installations using Kickstart, I wrote an article HERE last year on how to start converting some of your existing automation into using the new ESXi configstorecli, which is another article I recommend folks take a look if you have no already.
One of the challenges that I personally found when using configstorecli was purely figuring out the overall schema for the different components, groups and keys that are available. While I have demonstrated how to traverse the configstore in this blog post HERE, I still found experience less than ideal. I would have liked a bit more of an iterative exploration of the configstore itself and rather than showing the entire schema, I could slowly expect each node as configstore is a stored as a JSON document.