Support config flows about homeassistant-elasticsearch HOT 2 CLOSED

I’ve started this one a couple of times, but it seems that the more advanced configuration would be rather difficult to put into a flow from a UX perspective (e.g. custom certificate authorities, optional auth, entity/domain exclusions, ...).

I can put all the fields in, but that creates a cumbersome and confusing experience for users who just want to enter a URL.

Perhaps a middle ground is to enable basic config via a flow, with advanced config via yaml? This doesn’t seem like a common setup from the other components I’ve seen though, and I don’t love the arbitrary separation. I can also keep deferring this with hopes that config flows will become more robust in the future.

from homeassistant-elasticsearch.

Opened home-assistant/frontend#7820 to discuss the limitations of using an "options flow handler" as opposed to a custom config panel, like some internal integrations are capable of providing

from homeassistant-elasticsearch.