QuotaExtensions.GetCurrentUsagesBaseAsync Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Get the current usage of a resource.
- Request Path: /{scope}/providers/Microsoft.Quota/usages/{resourceName}
- Operation Id: Usages_Get
public static System.Threading.Tasks.Task<Azure.Response<Azure.ResourceManager.Quota.CurrentUsagesBaseResource>> GetCurrentUsagesBaseAsync (this Azure.ResourceManager.ArmClient client, Azure.Core.ResourceIdentifier scope, string resourceName, System.Threading.CancellationToken cancellationToken = default);
static member GetCurrentUsagesBaseAsync : Azure.ResourceManager.ArmClient * Azure.Core.ResourceIdentifier * string * System.Threading.CancellationToken -> System.Threading.Tasks.Task<Azure.Response<Azure.ResourceManager.Quota.CurrentUsagesBaseResource>>
<Extension()>
Public Function GetCurrentUsagesBaseAsync (client As ArmClient, scope As ResourceIdentifier, resourceName As String, Optional cancellationToken As CancellationToken = Nothing) As Task(Of Response(Of CurrentUsagesBaseResource))
Parameters
- scope
- ResourceIdentifier
The scope that the resource will apply against.
- resourceName
- String
Resource name for a given resource provider. For example:
- SKU name for Microsoft.Compute
- SKU or TotalLowPriorityCores for Microsoft.MachineLearningServices For Microsoft.Network PublicIPAddresses.
- cancellationToken
- CancellationToken
The cancellation token to use.
Returns
Exceptions
client
or resourceName
is null.
resourceName
is an empty string, and was expected to be non-empty.
Applies to
Colaborar conosco no GitHub
A fonte deste conteúdo pode ser encontrada no GitHub, onde você também pode criar e revisar problemas e solicitações de pull. Para obter mais informações, confira o nosso guia para colaboradores.
Azure SDK for .NET
Comentários
https://aka.ms/ContentUserFeedback.
Em breve: Ao longo de 2024, eliminaremos os problemas do GitHub como o mecanismo de comentários para conteúdo e o substituiremos por um novo sistema de comentários. Para obter mais informações, consulteEnviar e exibir comentários de