Like you I was staying put on an earlier version but I was looking at digging in somewhere. After reading all the new release notes and considering how trouble free testing an update is when you are using a container version of core HA I decided to move ahead to 0.113.0 and have now stopped at 0.113.2 for now and have not had any impact from loss of YAML config for my list of integrations. I am finding the improvement in the database that has come with 0.113.x has been fantastic so thanks to those who have worked hard on that! In fact I have NEVER been able to use âLogbookâ or âHistoryâ for more than a day or so after a new release until 0.113.x and in fact they load quite briskly on my QNAP NAS. Again congrats to all involved in that advance!
HahaâŚMaybe you could post this method as a PR to the HA YAML Documentation?
In any case this section is so far out of date and bordering on being utterly irrelevant right now:
Home Assistant uses the YAML syntax for configuration. YAML might take a while to get used to but is really powerful in allowing you to express complex configurations.
For integrations that you want to use in Home Assistant, you add code in your
configuration.yamlfile to specify its settings. This especially applies to integrations that are not yet available to configure through the UI.
I canât contribute to non-owned repositories without adding my employer as an owner, which I do not really fancy. Also, I kinda was told that my proposals are not very well welcomed, so I do not see if it would get approved 
Nonetheless, I would be happy if someone else adds it there.
I understand your situation. For my part I have looked at the process of editing the docs by adding a PR in the past to rectify errors or outdated rubbish and bailed out because it was simply too onerous a task.
And always with the possibility the PR will not be approved!
And as I type this I get this load of bilge shouting at me from the preview pane:
Encourage everyone to get involved in the conversation
Youâve replied 3 times to @nitobuendia in this particular topic!
A great discussion involves many voices and perspectives. Can you get anybody else involved?
And donât forget, if youâd like to continue your conversation with this particular user at length outside of public view, send them a personal message.
Yeah right!
Iâve been able to submit documentation PRs and get them approved, itâs honestly not that bad 
Thats good for you thenâŚkeep up the good work!
Letâs say I want to start with a clean HA install, I donât want to restore snapshots⌠Before with yaml, just overwrite the configuration.yaml file, and everything was setup⌠How to do it now with config flow?
So you want to partially restore a backup (the configuration.yaml part) but not the rest?
Indeed, just some integrations at once, like copy pasting some stuff from yaml file
I think you are out of luck.
But UI configs are generally quick and easy to set up.
Hmm, thatâs too bad , was so easy before
And has been discussed to death.
Is it possible too use secrets with config flow , like with add-ons?
Read the thread.
Addons donât use config flow but are configured in the addon as they always have been.
I know, I use secrets in add-ons , I was just wondering if secrets could also be used in config flow
I donât think so. Try it⌠you will likely find it will convert to text to put in .storage even if it worksâŚ
As far as I understand, no, you cannot. You will be prompted in the UI to input the data. Iâve gathered this as one of the user flows that are broken, but based on the answers, it doesnât seem like the NabuCasa team cares. Iâve posted quite a bit on alternatives to get back to YAML as well as why itâs a bad idea to remove YAML support.
Thereâs WTH season now, and some posted about YAML. While the WTH request was not complete (i.e. going to the detail or where it has and hasnât been deprecated), I thought some of you may want to upvote too.
You are flogging a dead horse. This is not going to change. You can take that to the bank.