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

MVP implementation of Backup sync agents #126122

Open
wants to merge 26 commits into
base: dev
Choose a base branch
from
Open

MVP implementation of Backup sync agents #126122

wants to merge 26 commits into from

Conversation

ludeeus
Copy link
Member

@ludeeus ludeeus commented Sep 17, 2024

Proposed change

Ref: home-assistant/architecture#1134

Based on the proposal above, this PR implements the MVP of backup sync agents.
As of now, this will only be invoked by the core backup integration.
Changes to allow these to be triggered in a supervisor environment will come in a different PR.


So this adds:

  • Allow integrations to define a async_get_backup_sync_agents function in the backup platform (as shown with the kitchen_sink integration)
  • Add 3 new WS handlers to the backup integration
  • Trigger backup sync if a backup is generated for the core backup integration by service call or WS.

Note that this PR does not yet add any tests, nor is related developer and user docs updated, this is on purpose as I expect the contents of this PR will change.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

@home-assistant
Copy link

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (backup) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of backup can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign backup Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@home-assistant
Copy link

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (demo) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of demo can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign demo Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

Copy link
Contributor

@epenet epenet left a comment

Choose a reason for hiding this comment

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

You only need to include what you want to expose in __all__

homeassistant/components/backup/__init__.py Outdated Show resolved Hide resolved
homeassistant/components/backup/__init__.py Outdated Show resolved Hide resolved
Copy link
Member

@MartinHjelmare MartinHjelmare left a comment

Choose a reason for hiding this comment

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

Looks good! Tests are missing. Some small comments and questions.

homeassistant/components/backup/base.py Outdated Show resolved Hide resolved
homeassistant/components/backup/websocket.py Outdated Show resolved Hide resolved
homeassistant/components/backup/websocket.py Show resolved Hide resolved
homeassistant/components/backup/sync_agent.py Outdated Show resolved Hide resolved
homeassistant/components/backup/sync_agent.py Outdated Show resolved Hide resolved
homeassistant/components/backup/__init__.py Outdated Show resolved Hide resolved
@home-assistant
Copy link

home-assistant bot commented Oct 1, 2024

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@home-assistant home-assistant bot marked this pull request as draft October 1, 2024 10:00
homeassistant/components/backup/websocket.py Outdated Show resolved Hide resolved
homeassistant/components/backup/websocket.py Outdated Show resolved Hide resolved
homeassistant/components/backup/websocket.py Outdated Show resolved Hide resolved
homeassistant/components/backup/models.py Outdated Show resolved Hide resolved
homeassistant/components/backup/sync_agent.py Outdated Show resolved Hide resolved
homeassistant/components/backup/websocket.py Outdated Show resolved Hide resolved
@ludeeus ludeeus marked this pull request as ready for review October 8, 2024 16:56
@MartinHjelmare
Copy link
Member

One test is failing.

@@ -313,8 +314,11 @@ async def test_agents_download(
}
)
with patch.object(BackupSyncAgentTest, "async_download_backup") as download_mock:
assert await client.receive_json()
assert snapshot == download_mock.call_args
assert snapshot == await client.receive_json()
Copy link
Member

Choose a reason for hiding this comment

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

Please put the expected value, in this case the snapshot, on the right side of the assertion.

@MartinHjelmare
Copy link
Member

When adding new websocket commands we normally wait with merging the core PR until there's an approved frontend PR. If the API is already settled with the frontend that may not be needed.

@MartinHjelmare
Copy link
Member

Mypy is failing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants