Skip to content

Added Ability to Check File Exists #69

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

Merged
merged 2 commits into from
Jun 16, 2025

Conversation

mitchelsellers
Copy link
Contributor

@mitchelsellers mitchelsellers commented Jun 16, 2025

Summary by CodeRabbit

  • New Features

    • Added a method to check if a blob exists in a specified Azure container using its full URL.
  • Chores

    • Upgraded several package dependencies to newer versions for improved stability and compatibility.

Copy link

coderabbitai bot commented Jun 16, 2025

Caution

Review failed

The pull request is closed.

"""

Walkthrough

The changes introduce a new method, BlobExists, to the Azure cloud storage provider interface and its implementation, enabling existence checks for blobs using a container name and full object URL. Additionally, several NuGet package dependencies are updated in both the main and test project files.

Changes

File(s) Change Summary
src/AspNetCore.Utilities.CloudStorage/AzureCloudStorageProvider.cs Added BlobExists method to interface and implementation for checking blob existence by URL.
src/AspNetCore.Utilities.CloudStorage/AspNetCore.Utilities.CloudStorage.csproj Upgraded Azure.Storage.Blobs and Microsoft.Extensions.DependencyInjection package versions.
src/AspNetCore.Utilities.CloudStorage.Tests/AspNetCore.Utilities.CloudStorage.Tests.csproj Upgraded coverlet.collector, Microsoft.NET.Test.Sdk, xunit, and xunit.runner.visualstudio packages.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant AzureCloudStorageProvider
    participant BlobServiceClient
    participant BlobContainerClient
    participant BlobClient

    Caller->>AzureCloudStorageProvider: BlobExists(expectedContainer, fullObjectUrl)
    AzureCloudStorageProvider->>AzureCloudStorageProvider: GetObjectName(fullObjectUrl)
    AzureCloudStorageProvider->>BlobServiceClient: new BlobServiceClient()
    AzureCloudStorageProvider->>BlobContainerClient: GetBlobContainerClient(expectedContainer)
    AzureCloudStorageProvider->>BlobClient: GetBlobClient(objectName)
    AzureCloudStorageProvider->>BlobClient: ExistsAsync()
    BlobClient-->>AzureCloudStorageProvider: Exists result
    AzureCloudStorageProvider-->>Caller: Return true/false
Loading

Assessment against linked issues

Objective Addressed Explanation
Add API to check if an asset exists by full path and by container/blobpath (#66)

Assessment against linked issues: Out-of-scope changes

Code Change Explanation
Upgrade of NuGet packages in project files (src/AspNetCore.Utilities.CloudStorage.csproj, src/AspNetCore.Utilities.CloudStorage.Tests.csproj) These changes relate to dependency management and are not explicitly required by the objectives in the linked issue. However, they do not affect the core functionality.

Possibly related PRs

Poem

A bunny hopped through code so bright,
To check if blobs exist at night.
With methods new and packages fresh,
It sniffed out bits in azure mesh.
Now storage checks are quick and neat—
This rabbit’s work is quite a feat! 🐇✨
"""


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 642dfd4 and cce6c17.

📒 Files selected for processing (3)
  • src/AspNetCore.Utilities.CloudStorage.Tests/AspNetCore.Utilities.CloudStorage.Tests.csproj (1 hunks)
  • src/AspNetCore.Utilities.CloudStorage/AspNetCore.Utilities.CloudStorage.csproj (1 hunks)
  • src/AspNetCore.Utilities.CloudStorage/AzureCloudStorageProvider.cs (3 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Commit Unit Tests in branch feature/update-for-existance
  • Post Copyable Unit Tests in Comment

🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @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 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.

@mitchelsellers mitchelsellers merged commit 0114e98 into develop Jun 16, 2025
2 of 3 checks passed
@mitchelsellers mitchelsellers deleted the feature/update-for-existance branch June 16, 2025 03:06
Copy link

@mitchelsellers mitchelsellers added the enhancement New feature or request label Jun 16, 2025
@mitchelsellers mitchelsellers changed the title Feature/update for existance Added Ability to Check File Exists Jun 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add Support for Exists Check
1 participant