Skip to content

Allow scheme to be specified when configuring Azurite #9570

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 1 commit into from
May 31, 2025

Conversation

MatthewSteeples
Copy link
Contributor

Description

Part of the work involved for #9381

Currently http is hardcoded when Aspire is configured to use Azurite. This change moves that into default configuration and allows it to be customised.

Checklist

  • Is this feature complete?
    • Yes. Ready to ship.
    • No. Follow-up changes expected.
  • Are you including unit tests for the changes and scenario tests if relevant?
    • Yes (existing tests updated)
    • No
  • Did you add public API?
    • Yes
      • If yes, did you have an API Review for it?
        • Yes
        • No
      • Did you add <remarks /> and <code /> elements on your triple slash comments?
        • Yes
        • No
    • No
  • Does the change make any security assumptions or guarantees?
    • Yes
      • If yes, have you done a threat model and had a security review?
        • Yes
        • No
    • No
  • Does the change require an update in our Aspire docs?

@Copilot Copilot AI review requested due to automatic review settings May 29, 2025 19:29
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR enhances Azurite configuration by allowing the scheme to be specified when building endpoints, rather than hardcoding "http".

  • Updated endpoints in the AzureStorageExtensions to accept a scheme parameter
  • Modified the connection string generation to use the configured scheme
  • Adjusted tests to verify the new scheme setting

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
tests/Aspire.Hosting.Azure.Tests/AzureStorageExtensionsTests.cs Added verification for the scheme configuration in tests
src/Aspire.Hosting.Azure.Storage/AzureStorageExtensions.cs Updated endpoint configuration to accept a scheme
src/Aspire.Hosting.Azure.Storage/AzureStorageEmulatorConnectionString.cs Modified connection string generation to include scheme

@github-actions github-actions bot added the area-integrations Issues pertaining to Aspire Integrations packages label May 29, 2025
@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates that the PR has been added by a community member label May 29, 2025
Copy link
Member

@davidfowl davidfowl left a comment

Choose a reason for hiding this comment

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

Actually we should be using WithHttpEndpoint

@dotnet-policy-service dotnet-policy-service bot added the needs-author-action An issue or pull request that requires more info or actions from the author. label May 30, 2025
@davidfowl davidfowl dismissed their stale review May 30, 2025 00:38

made change

@dotnet-policy-service dotnet-policy-service bot removed the needs-author-action An issue or pull request that requires more info or actions from the author. label May 30, 2025
@davidfowl davidfowl enabled auto-merge (squash) May 31, 2025 03:20
@davidfowl davidfowl merged commit 2a3758b into dotnet:main May 31, 2025
254 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-integrations Issues pertaining to Aspire Integrations packages community-contribution Indicates that the PR has been added by a community member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants