Commit c8d971c
docs: clarify baseline deployment name must match pricing config key
Add a comment in .env.example and a callout block in QUICKSTART.md
explaining that AZURE_BASELINE_DEPLOYMENT must match a key in the
pricing section of the config file. If a custom deployment name is used
(e.g. gpt-4o-baseline) without a matching pricing entry, baseline costs
are silently recorded as $0.0000 with no warning, making cost comparison
inaccurate.
Discovered while running evaluations against a Quick Deploy setup.
Applies to both Quick Deploy and Custom Deploy modes.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>1 parent 78720ac commit c8d971c
2 files changed
Lines changed: 5 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
9 | 12 | | |
10 | 13 | | |
11 | 14 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
139 | 139 | | |
140 | 140 | | |
141 | 141 | | |
| 142 | + | |
| 143 | + | |
142 | 144 | | |
143 | 145 | | |
144 | 146 | | |
| |||
0 commit comments