Refresh version context in the Azure OpenAI Terraform post #100

New issue

Open

opened 2026-08-10 20:08:24 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-10 20:08:24 +00:00

Collaborator

Context

src/pages/posts/azure-openai-terraform.md is dated 2023-10-11 and is one of the three posts selected for promotion and syndication. It is the highest-utility reference post in the set and the genre that performs best on dev.to, which means readers will copy the configuration verbatim.

A typo pass already landed in 1f36772. This issue covers the version staleness that pass deliberately left alone.

Problem

The configuration has aged out of accuracy in at least two places.

Both required_providers blocks pin azurerm = "~> 3". The 4.x major has been current for some time.
azurerm_cognitive_deployment.private deploys gpt-35-turbo version 0301, which Azure has retired. A reader applying this today gets a deployment failure, not a working prototype.
Several prerequisites are explicitly scoped "circa October 2023", including the claim that Azure OpenAI signup requires enterprise support.

Required outcome

The post stays honest about its vintage without pretending to be a current-day guide. The cheap, high-value fix is a dated-context note at the top rather than a full rewrite against azurerm 4.x.

Acceptance criteria

A short note near the top states the post was written in October 2023 against azurerm 3.x and that provider and model versions have moved since.
The gpt-35-turbo / 0301 deployment carries an inline note that the model version is retired and the reader should substitute a current deployment name.
Kai's voice and the post's structure are preserved. This is a banner plus two inline notes, not a rewrite.
Verify the current azurerm major and the model retirement status against Hashicorp and Microsoft docs before writing the note. Do not assert a version from memory.
ward exec build and ward exec pre-commit-all pass.

Non-goals

Rewriting the terraform against azurerm 4.x and re-verifying it against a live Azure subscription. That is a much larger job and would need a real subscription to validate.
Changing the post's security framing, which is still correct.

## Context `src/pages/posts/azure-openai-terraform.md` is dated 2023-10-11 and is one of the three posts selected for promotion and syndication. It is the highest-utility reference post in the set and the genre that performs best on dev.to, which means readers will copy the configuration verbatim. A typo pass already landed in `1f36772`. This issue covers the version staleness that pass deliberately left alone. ## Problem The configuration has aged out of accuracy in at least two places. * Both `required_providers` blocks pin `azurerm = "~> 3"`. The 4.x major has been current for some time. * `azurerm_cognitive_deployment.private` deploys `gpt-35-turbo` version `0301`, which Azure has retired. A reader applying this today gets a deployment failure, not a working prototype. * Several prerequisites are explicitly scoped "circa October 2023", including the claim that Azure OpenAI signup requires enterprise support. ## Required outcome The post stays honest about its vintage without pretending to be a current-day guide. The cheap, high-value fix is a dated-context note at the top rather than a full rewrite against azurerm 4.x. ## Acceptance criteria * A short note near the top states the post was written in October 2023 against azurerm 3.x and that provider and model versions have moved since. * The `gpt-35-turbo` / `0301` deployment carries an inline note that the model version is retired and the reader should substitute a current deployment name. * Kai's voice and the post's structure are preserved. This is a banner plus two inline notes, not a rewrite. * Verify the current azurerm major and the model retirement status against Hashicorp and Microsoft docs before writing the note. Do not assert a version from memory. * `ward exec build` and `ward exec pre-commit-all` pass. ## Non-goals * Rewriting the terraform against azurerm 4.x and re-verifying it against a live Azure subscription. That is a much larger job and would need a real subscription to validate. * Changing the post's security framing, which is still correct.

coilyco-ops added the

priority

autonomy

headless

labels

2026-08-10 20:09:44 +00:00

coilyco-ops added the

role/creator

role/ops

labels

2026-08-25 08:12:23 +00:00