Skip to content

Commit

Permalink
CodeGen from PR 19416 in Azure/azure-rest-api-specs
Browse files Browse the repository at this point in the history
Merge a5e497b1fe22a163e1c9a50f6d5d1eaa0d6210bf into 8ff7d5ef46f43875262110a4b2df7357bdf4369c
  • Loading branch information
SDKAuto committed Jun 28, 2022
1 parent c14ff07 commit 3aee903
Show file tree
Hide file tree
Showing 7 changed files with 49 additions and 14 deletions.
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
# Release History

## 1.0.0-beta.6 (Unreleased)
## 1.0.0-beta.1 (2022-06-28)

- Azure Resource Manager ApplicationInsights client library for Java. This package contains Microsoft Azure SDK for ApplicationInsights Management SDK. Composite Swagger for Application Insights Management Client. Package tag package-2022-04-01. For documentation on how to use this package, please see [Azure Management Libraries for Java](https://aka.ms/azsdk/java/mgmt).

### Features Added

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Various documentation is available to help you get started
<dependency>
<groupId>com.azure.resourcemanager</groupId>
<artifactId>azure-resourcemanager-applicationinsights</artifactId>
<version>1.0.0-beta.5</version>
<version>1.0.0-beta.6</version>
</dependency>
```
[//]: # ({x-version-update-end})
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -279,7 +279,7 @@ public ApplicationInsightsManager authenticate(TokenCredential credential, Azure
.append("-")
.append("com.azure.resourcemanager.applicationinsights")
.append("/")
.append("1.0.0-beta.5");
.append("1.0.0-beta.1");
if (!Configuration.getGlobalConfiguration().get("AZURE_TELEMETRY_DISABLED", false)) {
userAgentBuilder
.append(" (")
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,10 @@ Response<ApplicationInsightsComponentInner> updateTagsWithResponse(
* <p>In order to manage system resources, purge requests are throttled at 50 requests per hour. You should batch
* the execution of purge requests by sending a single command whose predicate includes all user identities that
* require purging. Use the in operator to specify multiple identities. You should run the query prior to using for
* a purge request to verify that the results are expected.
* a purge request to verify that the results are expected. Note: this operation is intended for Classic resources,
* for workspace-based Application Insights resource please run purge operation (directly on the
* workspace)(https://docs.microsoft.com/en-us/rest/api/loganalytics/workspace-purge/purge) , scoped to specific
* resource id.
*
* @param resourceGroupName The name of the resource group. The name is case insensitive.
* @param resourceName The name of the Application Insights component resource.
Expand All @@ -214,7 +217,10 @@ Response<ApplicationInsightsComponentInner> updateTagsWithResponse(
* <p>In order to manage system resources, purge requests are throttled at 50 requests per hour. You should batch
* the execution of purge requests by sending a single command whose predicate includes all user identities that
* require purging. Use the in operator to specify multiple identities. You should run the query prior to using for
* a purge request to verify that the results are expected.
* a purge request to verify that the results are expected. Note: this operation is intended for Classic resources,
* for workspace-based Application Insights resource please run purge operation (directly on the
* workspace)(https://docs.microsoft.com/en-us/rest/api/loganalytics/workspace-purge/purge) , scoped to specific
* resource id.
*
* @param resourceGroupName The name of the resource group. The name is case insensitive.
* @param resourceName The name of the Application Insights component resource.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -1153,7 +1153,10 @@ public Response<ApplicationInsightsComponentInner> updateTagsWithResponse(
* <p>In order to manage system resources, purge requests are throttled at 50 requests per hour. You should batch
* the execution of purge requests by sending a single command whose predicate includes all user identities that
* require purging. Use the in operator to specify multiple identities. You should run the query prior to using for
* a purge request to verify that the results are expected.
* a purge request to verify that the results are expected. Note: this operation is intended for Classic resources,
* for workspace-based Application Insights resource please run purge operation (directly on the
* workspace)(https://docs.microsoft.com/en-us/rest/api/loganalytics/workspace-purge/purge) , scoped to specific
* resource id.
*
* @param resourceGroupName The name of the resource group. The name is case insensitive.
* @param resourceName The name of the Application Insights component resource.
Expand Down Expand Up @@ -1215,7 +1218,10 @@ private Mono<Response<ComponentPurgeResponseInner>> purgeWithResponseAsync(
* <p>In order to manage system resources, purge requests are throttled at 50 requests per hour. You should batch
* the execution of purge requests by sending a single command whose predicate includes all user identities that
* require purging. Use the in operator to specify multiple identities. You should run the query prior to using for
* a purge request to verify that the results are expected.
* a purge request to verify that the results are expected. Note: this operation is intended for Classic resources,
* for workspace-based Application Insights resource please run purge operation (directly on the
* workspace)(https://docs.microsoft.com/en-us/rest/api/loganalytics/workspace-purge/purge) , scoped to specific
* resource id.
*
* @param resourceGroupName The name of the resource group. The name is case insensitive.
* @param resourceName The name of the Application Insights component resource.
Expand Down Expand Up @@ -1275,7 +1281,10 @@ private Mono<Response<ComponentPurgeResponseInner>> purgeWithResponseAsync(
* <p>In order to manage system resources, purge requests are throttled at 50 requests per hour. You should batch
* the execution of purge requests by sending a single command whose predicate includes all user identities that
* require purging. Use the in operator to specify multiple identities. You should run the query prior to using for
* a purge request to verify that the results are expected.
* a purge request to verify that the results are expected. Note: this operation is intended for Classic resources,
* for workspace-based Application Insights resource please run purge operation (directly on the
* workspace)(https://docs.microsoft.com/en-us/rest/api/loganalytics/workspace-purge/purge) , scoped to specific
* resource id.
*
* @param resourceGroupName The name of the resource group. The name is case insensitive.
* @param resourceName The name of the Application Insights component resource.
Expand All @@ -1298,7 +1307,10 @@ private Mono<ComponentPurgeResponseInner> purgeAsync(
* <p>In order to manage system resources, purge requests are throttled at 50 requests per hour. You should batch
* the execution of purge requests by sending a single command whose predicate includes all user identities that
* require purging. Use the in operator to specify multiple identities. You should run the query prior to using for
* a purge request to verify that the results are expected.
* a purge request to verify that the results are expected. Note: this operation is intended for Classic resources,
* for workspace-based Application Insights resource please run purge operation (directly on the
* workspace)(https://docs.microsoft.com/en-us/rest/api/loganalytics/workspace-purge/purge) , scoped to specific
* resource id.
*
* @param resourceGroupName The name of the resource group. The name is case insensitive.
* @param resourceName The name of the Application Insights component resource.
Expand All @@ -1319,7 +1331,10 @@ public ComponentPurgeResponseInner purge(String resourceGroupName, String resour
* <p>In order to manage system resources, purge requests are throttled at 50 requests per hour. You should batch
* the execution of purge requests by sending a single command whose predicate includes all user identities that
* require purging. Use the in operator to specify multiple identities. You should run the query prior to using for
* a purge request to verify that the results are expected.
* a purge request to verify that the results are expected. Note: this operation is intended for Classic resources,
* for workspace-based Application Insights resource please run purge operation (directly on the
* workspace)(https://docs.microsoft.com/en-us/rest/api/loganalytics/workspace-purge/purge) , scoped to specific
* resource id.
*
* @param resourceGroupName The name of the resource group. The name is case insensitive.
* @param resourceName The name of the Application Insights component resource.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -614,7 +614,10 @@ interface WithTags {
* <p>In order to manage system resources, purge requests are throttled at 50 requests per hour. You should batch
* the execution of purge requests by sending a single command whose predicate includes all user identities that
* require purging. Use the in operator to specify multiple identities. You should run the query prior to using for
* a purge request to verify that the results are expected.
* a purge request to verify that the results are expected. Note: this operation is intended for Classic resources,
* for workspace-based Application Insights resource please run purge operation (directly on the
* workspace)(https://docs.microsoft.com/en-us/rest/api/loganalytics/workspace-purge/purge) , scoped to specific
* resource id.
*
* @param body Describes the body of a request to purge data in a single table of an Application Insights component.
* @throws IllegalArgumentException thrown if parameters fail the validation.
Expand All @@ -630,7 +633,10 @@ interface WithTags {
* <p>In order to manage system resources, purge requests are throttled at 50 requests per hour. You should batch
* the execution of purge requests by sending a single command whose predicate includes all user identities that
* require purging. Use the in operator to specify multiple identities. You should run the query prior to using for
* a purge request to verify that the results are expected.
* a purge request to verify that the results are expected. Note: this operation is intended for Classic resources,
* for workspace-based Application Insights resource please run purge operation (directly on the
* workspace)(https://docs.microsoft.com/en-us/rest/api/loganalytics/workspace-purge/purge) , scoped to specific
* resource id.
*
* @param body Describes the body of a request to purge data in a single table of an Application Insights component.
* @param context The context to associate with this operation.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,10 @@ Response<ApplicationInsightsComponent> getByResourceGroupWithResponse(
* <p>In order to manage system resources, purge requests are throttled at 50 requests per hour. You should batch
* the execution of purge requests by sending a single command whose predicate includes all user identities that
* require purging. Use the in operator to specify multiple identities. You should run the query prior to using for
* a purge request to verify that the results are expected.
* a purge request to verify that the results are expected. Note: this operation is intended for Classic resources,
* for workspace-based Application Insights resource please run purge operation (directly on the
* workspace)(https://docs.microsoft.com/en-us/rest/api/loganalytics/workspace-purge/purge) , scoped to specific
* resource id.
*
* @param resourceGroupName The name of the resource group. The name is case insensitive.
* @param resourceName The name of the Application Insights component resource.
Expand All @@ -131,7 +134,10 @@ Response<ApplicationInsightsComponent> getByResourceGroupWithResponse(
* <p>In order to manage system resources, purge requests are throttled at 50 requests per hour. You should batch
* the execution of purge requests by sending a single command whose predicate includes all user identities that
* require purging. Use the in operator to specify multiple identities. You should run the query prior to using for
* a purge request to verify that the results are expected.
* a purge request to verify that the results are expected. Note: this operation is intended for Classic resources,
* for workspace-based Application Insights resource please run purge operation (directly on the
* workspace)(https://docs.microsoft.com/en-us/rest/api/loganalytics/workspace-purge/purge) , scoped to specific
* resource id.
*
* @param resourceGroupName The name of the resource group. The name is case insensitive.
* @param resourceName The name of the Application Insights component resource.
Expand Down

0 comments on commit 3aee903

Please sign in to comment.