Add MemoryProvider.EnsureMemoryStoreCreated create-if-missing helper to Foundry provider

[PratikDhanave (PratikDhanave)]

Adds an exported EnsureMemoryStoreCreated(ctx, chatModel, embeddingModel string, description *string) error method to the Foundry MemoryProvider.

What

• Retrieves the configured memory store via GetMemoryStore.
• If it exists, the call is a no-op (returns nil).
• If it is missing (HTTP 404), creates a MemoryStoreDefaultDefinition backed by the given chat and embedding model deployments, applying description when non-nil, and returns the create error.
• Any other retrieval error is returned unchanged.

Why

NewMemoryProvider documents that memoryStoreName must name an existing store, leaving no ergonomic way to provision one from Go. The .NET and Python Foundry providers expose an equivalent create-if-missing helper over their memory-store clients; this brings the Go port to parity so callers can bootstrap a store without dropping down to the internal azaiprojects client.

How tested

Table test in memory_test.go using the existing recording-transport harness:

• GET returns 200 -> returns nil, no POST.
• GET returns 404 -> POST /memory_stores with the chat/embedding model names and description in the body, returns nil.
• GET returns a non-404 error -> error propagated, no create issued.

[Copilot]

Pull request overview

Adds an exported helper on the Foundry MemoryProvider to provision the configured memory store on-demand, enabling Go callers to “create-if-missing” without using the internal Foundry client directly.

Changes:

• Added (*MemoryProvider).EnsureMemoryStoreCreated(...) which GETs the configured store and POSTs a default definition on HTTP 404.
• Added a table-driven test covering the exists / missing / non-404-error paths using the recording transport harness.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
provider/foundryprovider/memory.go	Adds EnsureMemoryStoreCreated to create the configured Foundry memory store when missing.
provider/foundryprovider/memory_test.go	Adds table tests validating no-op on 200, create on 404, and error propagation on non-404.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[PratikDhanave (PratikDhanave)]

Good catch — fixed in 02acc77: CreateMemoryStore now treats an HTTP 409 conflict as success, so a concurrent create between the GET (404) and the POST is a no-op. Added a test case covering the conflict path.

[github-actions]

Go API Consistency Review — PR #627

Scope: provider/foundryprovider/memory.go — new exported method EnsureMemoryStoreCreated

Upstream parity check

✅ .NET — aligned

dotnet/src/Microsoft.Agents.AI.Foundry/Memory/FoundryMemoryProvider.cs exposes:

public async Task EnsureMemoryStoreCreatedAsync(
    string chatModel,
    string embeddingModel,
    string? description = null,
    CancellationToken cancellationToken = default)

The Go signature EnsureMemoryStoreCreated(ctx context.Context, chatModel, embeddingModel string, description *string) error is semantically identical:

• Same positional arguments (chatModel, embeddingModel, optional description)
• *string for description mirrors .NET nullable string?
• context.Context replaces CancellationToken per Go idioms
• error return matches .NET throwing on create failure
• Create-if-missing logic (GET → 404 → POST) matches the internal .NET helper MemoryStoreExtensions.CreateMemoryStoreIfNotExistsAsync

⚠️ Python — no equivalent yet

python/packages/foundry/agent_framework_foundry/_memory_provider.py (FoundryMemoryProvider) does not expose an ensure_memory_store_created method. The PR description states Python has an equivalent, but the source only has before_run/after_run hooks — no create-if-missing public method.

This is a gap in the Python SDK, not a divergence introduced by this PR. The Go implementation correctly tracks the .NET surface. A follow-up to the upstream Python package would bring Python to parity.

Summary

This PR is approved for cross-repo parity against the .NET Foundry provider. The public-api-change label is correctly present. No parity issues are introduced by this change.

Generated by Go API Consistency Review Agent · sonnet46 · 28.9 AIC · ⌖ 5.66 AIC · ⊞ 5.7K · ◷