Skip to content

Clarify sample maturity tiers and add durable-state reference samples #640

Description

@andrewmatkin

Problem

The sample catalog does not clearly distinguish quickstart/starter samples from production-ready references, which makes it harder for users to know what can be copied into a real application versus what needs additional production hardening.

Scope

  • Document sample maturity tiers and a reusable README template.
  • Add durable Azure Blob Storage state starter samples across .NET, Node.js, and Python.
  • Add a .NET production-reference support triage sample with managed identity, Key Vault, Blob Storage, health checks, telemetry, Bicep infrastructure, tests, deployment guidance, and runbook.

Validation

  • .NET persistent-state build
  • .NET production-reference build and tests
  • Node persistent-state build
  • Python compile check
  • Repo lint
  • Plugin validation
  • Bicep build
  • Markdown link/fence validation

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions