Skip to content

Document Context Cache preflight workaround #4

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.

Sign up for GitHub

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
Saurabh Sensharma (saurabhsensharma) merged 1 commit into from
Aug 5, 2026
Merged

Document Context Cache preflight workaround #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -224,6 +224,17 @@ A pure CLI flow is also provided:
./scripts/deploy.ps1 -ResourceGroup rg-cc-demo -UseBicep # Bicep
```

The script uses ARM template-level validation as a temporary workaround for a
private-preview preflight issue. If you deploy the template directly with Azure
CLI, include the same validation setting:

```powershell
az deployment group create `
--resource-group rg-cc-demo `
--template-file azuredeploy.json `
--validation-level Template
```

---

## Repository layout
Expand Down Expand Up @@ -257,6 +268,7 @@ A pure CLI flow is also provided:
| `FeatureNotRegistered` on deploy | Run the three `az feature register` commands above and wait until each reports `Registered`. Email azurecontextcacherp@microsoft.com if state stays `Pending`. |
| `LocationNotAvailableForResourceType` | Only `centralus` (launch) and `swedencentral` are supported today. |
| `InvalidResourceName` | `namePrefix` must be 3–12 lowercase letters/digits. |
| `The context cache container could not be found or accessed` during preflight validation | Deploy with `az deployment group create ... --validation-level Template`, or use `scripts/deploy.ps1`, which applies this temporary private-preview workaround automatically. |
| Cache appears not to be used (no latency / cost improvement) | Confirm your prefix is **byte-identical** across requests, longer than a few hundred tokens, and that traffic is hitting the deployment created by this template (not a sibling deployment without `contextCacheContainerId`). |
| Need to unlink the cache later | PUT the same deployment with `properties.contextCacheContainerId` omitted (keep `sku` and `model` identical). |

Expand Down
12 changes: 11 additions & 1 deletion scripts/deploy.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,17 @@ if (-not (az group show --name $ResourceGroup 2>$null)) {

$template = if ($UseBicep) { Join-Path $root 'bicep/main.bicep' } else { Join-Path $root 'azuredeploy.json' }

$azArgs = @('deployment','group','create','--resource-group',$ResourceGroup,'--template-file',$template)
$azArgs = @(
'deployment',
'group',
'create',
'--resource-group',
$ResourceGroup,
'--template-file',
$template,
'--validation-level',
'Template'
)
if ($NamePrefix) { $azArgs += @('--parameters',"namePrefix=$NamePrefix") }

az @azArgs
Loading