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

Add location to backup download and remove APIs #5482

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

mdegat01
Copy link
Contributor

@mdegat01 mdegat01 commented Dec 11, 2024

Proposed change

Add location option to download and remove backup API to support cloud backup.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (which adds functionality to the supervisor)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

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
  • The code has been formatted using Ruff (ruff format supervisor tests)
  • Tests have been added to verify that the new code works.

If API endpoints or add-on configuration are added/changed:

Summary by CodeRabbit

  • New Features

    • Introduced a new schema for removing backups, allowing specification of multiple locations.
    • Enhanced the download functionality to support querying specific backup locations.
  • Bug Fixes

    • Improved error handling for backup downloads from invalid locations.
  • Tests

    • Added new tests for backup removal and download functionalities, covering specific location scenarios and error handling.
    • Refactored existing tests for clarity and maintainability, ensuring comprehensive coverage of backup operations.

@mdegat01 mdegat01 added the new-feature A new feature label Dec 11, 2024
@mdegat01 mdegat01 requested a review from agners December 11, 2024 22:06
Copy link

coderabbitai bot commented Dec 11, 2024

📝 Walkthrough

Walkthrough

The changes introduce a new schema for removing backups in the supervisor/api/backups.py file, which includes an optional ATTR_LOCATION field. The remove method is updated to validate this field, allowing for more flexible backup removal. Additionally, the download method is enhanced to handle location-specific requests more effectively. The test suite is expanded with new tests in tests/api/test_backups.py and tests/backups/test_manager.py, covering scenarios for backup removal and downloading from specific locations, as well as improving error handling.

Changes

File Change Summary
supervisor/api/backups.py Introduced SCHEMA_REMOVE schema with optional ATTR_LOCATION. Updated remove method to validate and handle locations. Enhanced download method to manage ATTR_LOCATION query parameter and improve response handling.
tests/api/test_backups.py Added tests: test_remove_backup_from_location, test_download_backup_from_location, and test_download_backup_from_invalid_location to cover backup removal and download scenarios.
tests/backups/test_manager.py Modified existing tests to use @pytest.mark.usefixtures. Expanded backup operation tests to handle multiple locations and refined error handling tests for various failure scenarios.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (5)
supervisor/api/backups.py (2)

422-431: Consider enhancing error handling for location validation.

While the implementation is correct, consider adding more specific error messages when location validation fails to help with debugging.

 if ATTR_LOCATION in body:
     self._validate_cloud_backup_location(request, body[ATTR_LOCATION])
-    locations = [self._location_to_mount(name) for name in body[ATTR_LOCATION]]
+    try:
+        locations = [self._location_to_mount(name) for name in body[ATTR_LOCATION]]
+    except APIError as err:
+        raise APIError(f"Invalid backup location: {err}") from err

437-444: Consider adding debug logging for location selection.

The location handling logic is correct, but adding debug logging would help track which location is being used for downloads.

 location = request.query.get(ATTR_LOCATION, backup.location) or None
 self._validate_cloud_backup_location(request, location)
+_LOGGER.debug("Downloading backup %s from location %s", backup.slug, location)
 if location not in backup.all_locations:
     raise APIError(f"Backup {backup.slug} is not in location {location}")
tests/api/test_backups.py (2)

752-772: Consider adding test for removing from multiple locations.

The test covers the basic case well, but consider adding a test case for removing a backup from multiple locations simultaneously.

@pytest.mark.usefixtures("tmp_supervisor_data")
async def test_remove_backup_from_multiple_locations(api_client: TestClient, coresys: CoreSys):
    """Test removing a backup from multiple locations."""
    backup_file = get_fixture_path("backup_example.tar")
    location_1 = Path(copy(backup_file, coresys.config.path_backup))
    location_2 = Path(copy(backup_file, coresys.config.path_core_backup))
    location_3 = Path(copy(backup_file, coresys.config.path_mounts / "backup_test"))

    await coresys.backups.reload()
    assert (backup := coresys.backups.get("7fed74c8"))

    resp = await api_client.delete(
        "/backups/7fed74c8",
        json={"location": [".cloud_backup", "backup_test"]}
    )
    assert resp.status == 200

    assert location_1.exists()
    assert not location_2.exists()
    assert not location_3.exists()
    assert coresys.backups.get("7fed74c8")

774-802: Consider testing content integrity after download.

The test verifies the download succeeds but doesn't verify the content integrity of the downloaded backup.

     with out_file.open("wb") as out:
         out.write(await resp.read())
 
     out_backup = Backup(coresys, out_file, "out", None)
     await out_backup.load()
-    assert backup == out_backup
+    # Verify backup content integrity
+    assert backup.slug == out_backup.slug
+    assert backup.name == out_backup.name
+    assert backup.date == out_backup.date
+    assert backup.compressed == out_backup.compressed
+    assert backup.protected == out_backup.protected
+    assert backup.homeassistant_version == out_backup.homeassistant_version
tests/backups/test_manager.py (1)

Line range hint 1980-1995: Consider adding error case test.

The test covers the success case well, but consider adding a test for error handling when removal fails.

@pytest.mark.usefixtures("tmp_supervisor_data")
async def test_backup_remove_multiple_locations_error(coresys: CoreSys):
    """Test error handling when removing backup from multiple locations."""
    backup_file = get_fixture_path("backup_example.tar")
    location_1 = Path(copy(backup_file, coresys.config.path_backup))
    location_2 = Path(copy(backup_file, coresys.config.path_core_backup))

    await coresys.backups.reload()
    assert (backup := coresys.backups.get("7fed74c8"))

    with patch("pathlib.Path.unlink", side_effect=OSError("Test error")):
        assert not coresys.backups.remove(backup)
        assert location_1.exists()
        assert location_2.exists()
        assert coresys.backups.get("7fed74c8")
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 774aef7 and 5757e65.

📒 Files selected for processing (3)
  • supervisor/api/backups.py (2 hunks)
  • tests/api/test_backups.py (1 hunks)
  • tests/backups/test_manager.py (2 hunks)
🔇 Additional comments (3)
supervisor/api/backups.py (1)

129-135: LGTM! Schema definition is well-structured.

The schema correctly validates the optional location field and reuses the existing _ensure_list helper for consistent list handling.

tests/api/test_backups.py (1)

805-811: LGTM! Error handling test is comprehensive.

The test properly verifies the error case for attempting to download from an invalid location.

tests/backups/test_manager.py (1)

Line range hint 1997-2014: LGTM! Test case is well-structured.

The test thoroughly verifies the partial removal functionality while ensuring the backup remains accessible from other locations.

location = request.query.get(ATTR_LOCATION, backup.location) or None
self._validate_cloud_backup_location(request, location)
if location not in backup.all_locations:
raise APIError(f"Backup {backup.slug} is not in location {location}")
Copy link
Member

Choose a reason for hiding this comment

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

Should that be an APINotFound error maybe? 🤔 I mean it is query string dependent, so not REST, maybe 404 is not appropriate then 🤔

Copy link
Contributor Author

@mdegat01 mdegat01 Dec 12, 2024

Choose a reason for hiding this comment

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

Yea that was my thought process. The resource is the backup not the location so I left that as a 400, it felt more like invalid input. I could go either way though I suppose.

@agners agners merged commit 02ceb71 into main Dec 12, 2024
21 checks passed
@agners agners deleted the add-location-backup-apis branch December 12, 2024 18:44
@github-actions github-actions bot locked and limited conversation to collaborators Dec 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants