[BUG] Nuget official package of Microsoft.Azure.Management.Consumption is not in sync with GitHub code
See original GitHub issueLibrary name and version
Microsoft.Azure.Management.Consumption 3.0.2
Describe the bug
The code on the repository (https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/consumption/Microsoft.Azure.Management.Consumption/src/Generated/UsageDetailsOperationsExtensions.cs) contains the scope parameter but the nuget package officially release does not:
Code in GitHub
public static async Task<IPage<UsageDetail>> ListAsync(this IUsageDetailsOperations operations, string scope, string expand = default(string), string filter = default(string), string skiptoken = default(string), int? top = default(int?), string metric = default(string), CancellationToken cancellationToken = default(CancellationToken))
{
using (var _result = await operations.ListWithHttpMessagesAsync(scope, expand, filter, skiptoken, top, metric, null, cancellationToken).ConfigureAwait(false))
{
return _result.Body;
}
}
SDK:
This has been almost 1yr and 4 months since this has been asked by the community here. https://github.com/Azure/azure-sdk-for-net/issues/14602
What’s going on? This needs to be released ASAP . 1yr and 4 months later and the code is not in sync with the current official latest release.
Please advise ASAP.
Expected behavior
The nuget package contains the source code that is shown on the repository.
Actual behavior
The code released in the nuget package does not contains the scope.
Reproduction Steps
in a console
dotnet new console --name Demo
dotnet add package Microsoft.Azure.Management.Consumption --version 3.0.2
In the code:
using Microsoft.Azure.Management.Consumption;
using Microsoft.Rest;
var credentials = new TokenCredentials(string.Empty);
var client = new ConsumptionManagementClient(credentials);
await client.UsageDetails.ListAsync();
intellisense doesn’t show the scope parameter.
Environment
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:11 (2 by maintainers)
Top GitHub Comments
@tujamg Seems kind of long to release things that are already committed in the main branch…
Consumption cmdlet version update is in our backlog. Will update this issue once we release a new version.