Repository navigation
Conversation
Route immutable byte operations through an artifacts domain with explicit filesystem or managed-identity Azure Blob selection. Validate configured storage without adding product routes. Co-authored-by: Ben Thomas <25218250+alliscode@users.noreply.github.com> Co-authored-by: Nishiki <1121087+nshki@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Copilot was unable to review this pull request because there is no eligible user to bill.
An enterprise owner can allow the organization to be billed for reviews like this by enabling Copilot code review for users without a license.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Hub needs one artifact contract so product domains do not depend on Azure SDK calls. This is the second layer of #171, based on the production runtime.
What changes
The artifacts domain selects filesystem or managed-identity Azure Blob storage and exposes immutable byte reads, writes, and deletion. It validates opaque keys, bounds each artifact to 32 MiB, and returns explicit failure results without provider details.
Startup validates explicitly configured storage, with no silent provider fallback. This is a storage foundation, not Build import, preview hosting, or product authorization. Real Azure identity and Blob access remain unverified in a live tenant.
Created from a Slack conversation with @alliscode.