Add multi-provider secret sync - #239
Merged
Merged
Conversation
Add per-item provider placement, conflict-aware reconciliation, Local Vault-first background work, and live provider status updates across secrets, keystores, certificates, provisioning profiles, and publish profiles. Add provider defaults, persistent task history, per-provider progress, shared picker UI, identity persistence, and macOS development reliability fixes. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 10500b7f-7c58-406a-96e8-e7c6f13b5ad6
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.
MAUI Sherpa currently treats cloud secret storage as a single active-provider choice, which prevents users from keeping each sensitive item in the provider set that best fits its backup and publishing needs. This change adds item-level multi-provider placement with progressive status and recoverable background reconciliation.
What changed
Review notes
Background records contain only item/provider references and state. They persist through Local Vault when available and fall back to memory-only execution when it is unavailable. Reconciliation is still represented as one logical item job with provider substeps; independent provider-lane scheduling is intentionally deferred so source selection, revisions, coalescing, and conflict decisions cannot diverge.
Validation
dotnet test tests/MauiSherpa.Core.Tests/MauiSherpa.Core.Tests.csproj(552 passed)dotnet build src/MauiSherpa.MacOS -f net10.0-macos --no-restore --verbosity minimal