KustoClusterResource.GetKustoAttachedDatabaseConfiguration 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.
Returns an attached database configuration.
- Request Path: /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Kusto/clusters/{clusterName}/attachedDatabaseConfigurations/{attachedDatabaseConfigurationName}
- Operation Id: AttachedDatabaseConfigurations_Get
public virtual Azure.Response<Azure.ResourceManager.Kusto.KustoAttachedDatabaseConfigurationResource> GetKustoAttachedDatabaseConfiguration (string attachedDatabaseConfigurationName, System.Threading.CancellationToken cancellationToken = default);
abstract member GetKustoAttachedDatabaseConfiguration : string * System.Threading.CancellationToken -> Azure.Response<Azure.ResourceManager.Kusto.KustoAttachedDatabaseConfigurationResource>
override this.GetKustoAttachedDatabaseConfiguration : string * System.Threading.CancellationToken -> Azure.Response<Azure.ResourceManager.Kusto.KustoAttachedDatabaseConfigurationResource>
Public Overridable Function GetKustoAttachedDatabaseConfiguration (attachedDatabaseConfigurationName As String, Optional cancellationToken As CancellationToken = Nothing) As Response(Of KustoAttachedDatabaseConfigurationResource)
Parameters
- attachedDatabaseConfigurationName
- String
The name of the attached database configuration.
- cancellationToken
- CancellationToken
The cancellation token to use.
Returns
Exceptions
attachedDatabaseConfigurationName
is null.
attachedDatabaseConfigurationName
is an empty string, and was expected to be non-empty.
Applies to
Met ons samenwerken op GitHub
De bron voor deze inhoud vindt u op GitHub, waar u ook problemen en pull-aanvragen kunt maken en controleren. Bekijk onze gids voor inzenders voor meer informatie.
Azure SDK for .NET
Feedback
https://aka.ms/ContentUserFeedback.
Binnenkort beschikbaar: In de loop van 2024 zullen we GitHub-problemen geleidelijk uitfaseren als het feedbackmechanisme voor inhoud en deze vervangen door een nieuw feedbacksysteem. Zie voor meer informatie:Feedback verzenden en weergeven voor