AzureDataFactoryClient uses rejected 2017 preview API version

Open Beginner friendly
#256 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
azure, csharp
Domain
api, cloud

Research direction

Start in src/Azure.Connectors.Sdk/Generated/AzureDataFactoryExtensions.cs at ListSubscriptionsAsync, then inspect the other generated Data Factory management paths for the rejected API version. Confirm the requests use a supported version and run the deployed end-to-end coverage mentioned in the issue to verify the connector no longer returns HTTP 400.

Written by the indexing model from the issue text.

Description

Description

AzureDataFactoryClient.ListSubscriptionsAsync in Azure.Connectors.Sdk 0.14.0-preview.1 generates this connector request:

GET /subscriptions?x-ms-api-version=2017-09-01-preview

The live Azure Data Factory connector rejects that request with HTTP 400:

InvalidApiVersionParameter: The api-version '2017-09-01-preview' is invalid.

The current supported version list returned by ARM starts with 2026-06-01, 2025-04-01, and other active versions; it does not include 2017-09-01-preview.

Source

src/Azure.Connectors.Sdk/Generated/AzureDataFactoryExtensions.cs

The stale version appears on ListSubscriptionsAsync and the other generated Data Factory management paths.

Validation

  • Package: Azure.Connectors.Sdk 0.14.0-preview.1
  • Client: AzureDataFactoryClient
  • Connection: authenticated Connector Namespace Azure Data Factory connection
  • Result: generated client reaches the connector, which returns HTTP 400 before any data is returned

This was found while adding deployed end-to-end coverage for the 0.14 samples update.

Authored with Dobby.

Dominant language
C#
Stars
3
Forks
5
Avg merge
2d 56m
Merged PRs (30d)
8

Contributor guide

Open the 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/Connectors-NET-SDK

All issues in Azure/Connectors-NET-SDK

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.