Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support API version 2026-04-01

Open
  • Is something wrong?
#95 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp
Domain
api, backend

Research direction

Start with src/Azure.AppConfiguration.Emulator.Versioning/ApiVersions.cs and compare the existing 2024-09-01 support with the published 2026-04-01 REST references and Azure REST API specifications. Trace the emulator's snapshot handling to determine the required operation-status behavior; done means the new API version and its documented snapshot LRO surface are supported.

Written by the indexing model from the issue text.

Description

The currently supported versions of App Configuration Emulator don't include version 2026-04-01 of the Data plane API yet. Can the emulator be updated to support this new version?

Based on the published REST API references and the Azure REST API specifications repository, the 2026-04-01 data-plane version appears to be an evolutionary update over 2024-09-01, with the most notable addition being explicit support for tracking long-running operations (LROs) for snapshot-related operations.

Summary of the changes generated with Copilot:

Area 2024-09-01 2026-04-01 Difference
Long-running operation status endpoint No dedicated GET /operations endpoint is documented in this version. Snapshot creation returns an Operation-Location header. New GET /operations?snapshot={name} endpoint returns operation state (Running, etc.), operation ID, error details, and retry information. New capability: clients can explicitly poll operation status rather than relying solely on response headers.
Snapshot operation model Snapshot creation supports asynchronous behavior via the Operation-Location response header. Snapshot operations are integrated with a documented long-running operation (LRO) pattern that includes a dedicated status resource. More complete LRO support and a clearer REST contract for asynchronous snapshot processing.
Operation status schema Not documented as a public resource. Introduces an Operation Details resource containing id, status, and structured error information. New resource type exposed by the API.
Error model Uses App Configuration error objects. Adds Azure Core-style error definitions for operation tracking responses (Error, InnerError, detailed error hierarchy). Expanded error contract for operation-status APIs.
Overall resource set Includes keys, key-values, labels, revisions, locks, and snapshot APIs. Retains existing resource areas and adds documented operation-tracking APIs. No major resource removals observed; API surface is extended rather than replaced.
Dominant language
C#
Stars
38
Forks
8
Avg merge
1m
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AppConfiguration-Emulator

All issues in Azure/AppConfiguration-Emulator

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.