Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle new API / Frontend early boot #1770

Merged
merged 5 commits into from
Jun 2, 2020
Merged

Conversation

pvizeli
Copy link
Member

@pvizeli pvizeli commented Jun 2, 2020

Avoid also log flooding because we restart Core.

90% of the code is for P2 and the other 10% for P1. Since we need anyway touch the code and change the logic. The P1 adds the 503 for API which makes this PR a lot simpler.

@pvizeli pvizeli marked this pull request as ready for review June 2, 2020 11:54
@pvizeli pvizeli merged commit af412c3 into dev Jun 2, 2020
@delete-merged-branch delete-merged-branch bot deleted the new-api-frontend-handling branch June 2, 2020 12:54
status = resp.status
_LOGGER.warning("Home Assistant API config mismatch: %s", status)
data = await resp.json()
if data.get("state", "RUNNING") == "RUNNING":
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why would we wait on running for the rollback check? The frontend would be up already the user would be able to configure or fix whatever problem there could be, so why not just check if the frontend is up?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's merge P2 and we can start to play with that. You can after P2 start to add new integration or remove integration etc while HA is startup? We can later split up the check for block startup and API proxy 👍

@lock lock bot locked and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants