text:
Docs.MS Release Updates for azure-storage-queue

Update docs metadata and targeting for release of azure-storage-queue

Docs Build status updates of commit 4870929:
:clock10: Full build: the average full build time is 97 min(s) 49 sec(s), this is based on the last 823 build(s) for this repository.

Docs Build status updates of commit 4870929:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/storage-queue-readme-pre.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

legacy/docs-ref-autogen/overview/EventHubs/Client.yml
:warning:Warning
View (azure-java-legacy)
Details

docs-ref-autogen/com.microsoft.azure.management.monitor.yml
:warning:Warning
View (azure-java-stable)
Details

package.json
:white_check_mark:Succeeded

docs-ref-services/storage-queue-readme-pre.md

Line 221: [Warning-InvalidBookmark] Invalid link: 'Dequeue messages from a queue'. The file docs-ref-services/storage-queue-readme-pre.md doesn't contain a bookmark named 'dequeue-messages-from-a-queue'.
Line 221: [Warning-InvalidBookmark] Invalid link: 'Dequeue messages from a queue'. The file docs-ref-services/storage-queue-readme-pre.md doesn't contain a bookmark named 'dequeue-messages-from-a-queue'.
Line 221: [Warning-InvalidBookmark] Invalid link: 'Dequeue messages from a queue'. The file docs-ref-services/storage-queue-readme-pre.md doesn't contain a bookmark named 'dequeue-messages-from-a-queue'.

legacy/docs-ref-autogen/overview/EventHubs/Client.yml

[Warning-DuplicateUids] Uid(azure.java.sdk.landingpage.services.eventhub.Client) has already been defined in docs-ref-services/messaging-eventhubs-readme.md.

docs-ref-autogen/com.microsoft.azure.management.monitor.yml

[Warning-InvalidBookmark] Invalid link: 'ActionGroup.DefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActionGroup.DefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActionGroup_DefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'ActionGroup.DefinitionStages.WithCreate'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActionGroup.DefinitionStages.WithCreate.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActionGroup_DefinitionStages_WithCreate'.
[Warning-InvalidBookmark] Invalid link: 'ActionGroup.UpdateStages.WithActionDefinition'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActionGroup.UpdateStages.WithActionDefinition.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActionGroup_UpdateStages_WithActionDefinition'.
[Warning-InvalidBookmark] Invalid link: 'ActionGroup.UpdateStages.WithActionUpdateDefinition'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActionGroup.UpdateStages.WithActionUpdateDefinition.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActionGroup_UpdateStages_WithActionUpdateDefinition'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogAlert.DefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogAlert.DefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogAlert_DefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogAlert.DefinitionStages.WithActionGroup'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogAlert.DefinitionStages.WithActionGroup.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogAlert_DefinitionStages_WithActionGroup'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogAlert.DefinitionStages.WithAlertEnabled'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogAlert.DefinitionStages.WithAlertEnabled.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogAlert_DefinitionStages_WithAlertEnabled'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogAlert.DefinitionStages.WithCreate'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogAlert.DefinitionStages.WithCreate.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogAlert_DefinitionStages_WithCreate'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogAlert.DefinitionStages.WithCriteriaDefinition'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogAlert.DefinitionStages.WithCriteriaDefinition.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogAlert_DefinitionStages_WithCriteriaDefinition'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogAlert.DefinitionStages.WithDescription'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogAlert.DefinitionStages.WithDescription.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogAlert_DefinitionStages_WithDescription'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogAlert.DefinitionStages.WithScopes'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogAlert.DefinitionStages.WithScopes.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogAlert_DefinitionStages_WithScopes'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogAlert.UpdateStages.WithActivityLogUpdate'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogAlert.UpdateStages.WithActivityLogUpdate.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogAlert_UpdateStages_WithActivityLogUpdate'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogs.ActivityLogsQueryDefinitionStages.WithActivityLogsQueryExecute'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogs.ActivityLogsQueryDefinitionStages.WithActivityLogsQueryExecute.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogs_ActivityLogsQueryDefinitionStages_WithActivityLogsQueryExecute'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogs.ActivityLogsQueryDefinitionStages.WithActivityLogsSelectFilter'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogs.ActivityLogsQueryDefinitionStages.WithActivityLogsSelectFilter.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogs_ActivityLogsQueryDefinitionStages_WithActivityLogsSelectFilter'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogs.ActivityLogsQueryDefinitionStages.WithEventDataEndFilter'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogs.ActivityLogsQueryDefinitionStages.WithEventDataEndFilter.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogs_ActivityLogsQueryDefinitionStages_WithEventDataEndFilter'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogs.ActivityLogsQueryDefinitionStages.WithEventDataFieldFilter'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogs.ActivityLogsQueryDefinitionStages.WithEventDataFieldFilter.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogs_ActivityLogsQueryDefinitionStages_WithEventDataFieldFilter'.
[Warning-InvalidBookmark] Invalid link: 'ActivityLogs.ActivityLogsQueryDefinitionStages.WithEventDataStartTimeFilter'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ActivityLogs.ActivityLogsQueryDefinitionStages.WithEventDataStartTimeFilter.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ActivityLogs_ActivityLogsQueryDefinitionStages_WithEventDataStartTimeFilter'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleProfile.DefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleProfile.DefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleProfile_DefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleProfile.DefinitionStages.WithAttach'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleProfile.DefinitionStages.WithAttach.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleProfile_DefinitionStages_WithAttach'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleProfile.DefinitionStages.WithScaleRule'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleProfile.DefinitionStages.WithScaleRule.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleProfile_DefinitionStages_WithScaleRule'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleProfile.DefinitionStages.WithScaleRuleOptional'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleProfile.DefinitionStages.WithScaleRuleOptional.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleProfile_DefinitionStages_WithScaleRuleOptional'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleProfile.DefinitionStages.WithScaleSchedule'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleProfile.DefinitionStages.WithScaleSchedule.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleProfile_DefinitionStages_WithScaleSchedule'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleProfile.UpdateDefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleProfile.UpdateDefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleProfile_UpdateDefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleProfile.UpdateDefinitionStages.WithAttach'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleProfile.UpdateDefinitionStages.WithAttach.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleProfile_UpdateDefinitionStages_WithAttach'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleProfile.UpdateDefinitionStages.WithScaleRule'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleProfile.UpdateDefinitionStages.WithScaleRule.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleProfile_UpdateDefinitionStages_WithScaleRule'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleProfile.UpdateDefinitionStages.WithScaleRuleOptional'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleProfile.UpdateDefinitionStages.WithScaleRuleOptional.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleProfile_UpdateDefinitionStages_WithScaleRuleOptional'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleProfile.UpdateDefinitionStages.WithScaleSchedule'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleProfile.UpdateDefinitionStages.WithScaleSchedule.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleProfile_UpdateDefinitionStages_WithScaleSchedule'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleSetting.DefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleSetting.DefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleSetting_DefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleSetting.DefinitionStages.DefineAutoscaleSettingResourceNotifications'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleSetting.DefinitionStages.DefineAutoscaleSettingResourceNotifications.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleSetting_DefinitionStages_DefineAutoscaleSettingResourceNotifications'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleSetting.DefinitionStages.DefineAutoscaleSettingResourceProfiles'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleSetting.DefinitionStages.DefineAutoscaleSettingResourceProfiles.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleSetting_DefinitionStages_DefineAutoscaleSettingResourceProfiles'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleSetting.DefinitionStages.WithAutoscaleSettingResourceEnabled'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleSetting.DefinitionStages.WithAutoscaleSettingResourceEnabled.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleSetting_DefinitionStages_WithAutoscaleSettingResourceEnabled'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleSetting.DefinitionStages.WithAutoscaleSettingResourceTargetResourceUri'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleSetting.DefinitionStages.WithAutoscaleSettingResourceTargetResourceUri.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleSetting_DefinitionStages_WithAutoscaleSettingResourceTargetResourceUri'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleSetting.DefinitionStages.WithCreate'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleSetting.DefinitionStages.WithCreate.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleSetting_DefinitionStages_WithCreate'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleSetting.DefinitionStages.WithGroup'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleSetting.DefinitionStages.WithGroup.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleSetting_DefinitionStages_WithGroup'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleSetting.UpdateStages.DefineAutoscaleSettingProfiles'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleSetting.UpdateStages.DefineAutoscaleSettingProfiles.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleSetting_UpdateStages_DefineAutoscaleSettingProfiles'.
[Warning-InvalidBookmark] Invalid link: 'AutoscaleSetting.UpdateStages.UpdateAutoscaleSettings'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.AutoscaleSetting.UpdateStages.UpdateAutoscaleSettings.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_AutoscaleSetting_UpdateStages_UpdateAutoscaleSettings'.
[Warning-InvalidBookmark] Invalid link: 'DiagnosticSetting.DefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.DiagnosticSetting.DefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_DiagnosticSetting_DefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'DiagnosticSetting.DefinitionStages.WithCreate'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.DiagnosticSetting.DefinitionStages.WithCreate.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_DiagnosticSetting_DefinitionStages_WithCreate'.
[Warning-InvalidBookmark] Invalid link: 'DiagnosticSetting.DefinitionStages.WithDiagnosticLogRecipient'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.DiagnosticSetting.DefinitionStages.WithDiagnosticLogRecipient.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_DiagnosticSetting_DefinitionStages_WithDiagnosticLogRecipient'.
[Warning-InvalidBookmark] Invalid link: 'DiagnosticSetting.UpdateStages.WithEventHub'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.DiagnosticSetting.UpdateStages.WithEventHub.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_DiagnosticSetting_UpdateStages_WithEventHub'.
[Warning-InvalidBookmark] Invalid link: 'DiagnosticSetting.UpdateStages.WithLogAnalytics'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.DiagnosticSetting.UpdateStages.WithLogAnalytics.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_DiagnosticSetting_UpdateStages_WithLogAnalytics'.
[Warning-InvalidBookmark] Invalid link: 'DiagnosticSetting.UpdateStages.WithMetricAndLogs'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.DiagnosticSetting.UpdateStages.WithMetricAndLogs.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_DiagnosticSetting_UpdateStages_WithMetricAndLogs'.
[Warning-InvalidBookmark] Invalid link: 'DiagnosticSetting.UpdateStages.WithStorageAccount'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.DiagnosticSetting.UpdateStages.WithStorageAccount.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_DiagnosticSetting_UpdateStages_WithStorageAccount'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithActionGroup'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithActionGroup.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithActionGroup'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithActionGroupMultipleResource'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithActionGroupMultipleResource.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithActionGroupMultipleResource'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithCreate'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithCreate.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithCreate'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithCreateDynamicCondition'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithCreateDynamicCondition.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithCreateDynamicCondition'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithCriteriaDefinition'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithCriteriaDefinition.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithCriteriaDefinition'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithCriteriaDefinitionMultipleResource'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithCriteriaDefinitionMultipleResource.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithCriteriaDefinitionMultipleResource'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithEvaluationFrequency'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithEvaluationFrequency.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithEvaluationFrequency'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithEvaluationFrequencyMultipleResource'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithEvaluationFrequencyMultipleResource.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithEvaluationFrequencyMultipleResource'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithScopes'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithScopes.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithScopes'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithSeverity'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithSeverity.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithSeverity'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithSeverityMultipleResource'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithSeverityMultipleResource.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithSeverityMultipleResource'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithWindowSize'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithWindowSize.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithWindowSize'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.DefinitionStages.WithWindowSizeMultipleResource'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.DefinitionStages.WithWindowSizeMultipleResource.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_DefinitionStages_WithWindowSizeMultipleResource'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlert.UpdateStages.WithMetricUpdate'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlert.UpdateStages.WithMetricUpdate.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlert_UpdateStages_WithMetricUpdate'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlertCondition.DefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlertCondition.DefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlertCondition_DefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlertCondition.DefinitionStages.Blank.MetricName<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlertCondition.DefinitionStages.Blank.MetricName.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlertCondition_DefinitionStages_Blank_MetricName'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlertCondition.DefinitionStages.WithConditionAttach<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlertCondition.DefinitionStages.WithConditionAttach.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlertCondition_DefinitionStages_WithConditionAttach'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlertCondition.DefinitionStages.WithCriteriaOperator<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlertCondition.DefinitionStages.WithCriteriaOperator.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlertCondition_DefinitionStages_WithCriteriaOperator'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlertCondition.UpdateDefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlertCondition.UpdateDefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlertCondition_UpdateDefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlertCondition.UpdateDefinitionStages.Blank.MetricName<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlertCondition.UpdateDefinitionStages.Blank.MetricName.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlertCondition_UpdateDefinitionStages_Blank_MetricName'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlertCondition.UpdateDefinitionStages.WithConditionAttach<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlertCondition.UpdateDefinitionStages.WithConditionAttach.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlertCondition_UpdateDefinitionStages_WithConditionAttach'.
[Warning-InvalidBookmark] Invalid link: 'MetricAlertCondition.UpdateDefinitionStages.WithCriteriaOperator<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricAlertCondition.UpdateDefinitionStages.WithCriteriaOperator.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricAlertCondition_UpdateDefinitionStages_WithCriteriaOperator'.
[Warning-InvalidBookmark] Invalid link: 'MetricDefinition.MetricsQueryDefinitionStages.WithMetricEndFilter'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDefinition.MetricsQueryDefinitionStages.WithMetricEndFilter.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDefinition_MetricsQueryDefinitionStages_WithMetricEndFilter'.
[Warning-InvalidBookmark] Invalid link: 'MetricDefinition.MetricsQueryDefinitionStages.WithMetricStartTimeFilter'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDefinition.MetricsQueryDefinitionStages.WithMetricStartTimeFilter.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDefinition_MetricsQueryDefinitionStages_WithMetricStartTimeFilter'.
[Warning-InvalidBookmark] Invalid link: 'MetricDefinition.MetricsQueryDefinitionStages.WithMetricsQueryExecute'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDefinition.MetricsQueryDefinitionStages.WithMetricsQueryExecute.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDefinition_MetricsQueryDefinitionStages_WithMetricsQueryExecute'.
[Warning-InvalidBookmark] Invalid link: 'MetricDynamicAlertCondition.DefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDynamicAlertCondition.DefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDynamicAlertCondition_DefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'MetricDynamicAlertCondition.DefinitionStages.Blank.MetricName<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDynamicAlertCondition.DefinitionStages.Blank.MetricName.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDynamicAlertCondition_DefinitionStages_Blank_MetricName'.
[Warning-InvalidBookmark] Invalid link: 'MetricDynamicAlertCondition.DefinitionStages.WithConditionAttach<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDynamicAlertCondition.DefinitionStages.WithConditionAttach.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDynamicAlertCondition_DefinitionStages_WithConditionAttach'.
[Warning-InvalidBookmark] Invalid link: 'MetricDynamicAlertCondition.DefinitionStages.WithCriteriaOperator<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDynamicAlertCondition.DefinitionStages.WithCriteriaOperator.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDynamicAlertCondition_DefinitionStages_WithCriteriaOperator'.
[Warning-InvalidBookmark] Invalid link: 'MetricDynamicAlertCondition.DefinitionStages.WithFailingPeriods<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDynamicAlertCondition.DefinitionStages.WithFailingPeriods.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDynamicAlertCondition_DefinitionStages_WithFailingPeriods'.
[Warning-InvalidBookmark] Invalid link: 'MetricDynamicAlertCondition.UpdateDefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDynamicAlertCondition.UpdateDefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDynamicAlertCondition_UpdateDefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'MetricDynamicAlertCondition.UpdateDefinitionStages.Blank.MetricName<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDynamicAlertCondition.UpdateDefinitionStages.Blank.MetricName.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDynamicAlertCondition_UpdateDefinitionStages_Blank_MetricName'.
[Warning-InvalidBookmark] Invalid link: 'MetricDynamicAlertCondition.UpdateDefinitionStages.WithConditionAttach<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDynamicAlertCondition.UpdateDefinitionStages.WithConditionAttach.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDynamicAlertCondition_UpdateDefinitionStages_WithConditionAttach'.
[Warning-InvalidBookmark] Invalid link: 'MetricDynamicAlertCondition.UpdateDefinitionStages.WithCriteriaOperator<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDynamicAlertCondition.UpdateDefinitionStages.WithCriteriaOperator.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDynamicAlertCondition_UpdateDefinitionStages_WithCriteriaOperator'.
[Warning-InvalidBookmark] Invalid link: 'MetricDynamicAlertCondition.UpdateDefinitionStages.WithFailingPeriods<ParentT>'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.MetricDynamicAlertCondition.UpdateDefinitionStages.WithFailingPeriods.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_MetricDynamicAlertCondition_UpdateDefinitionStages_WithFailingPeriods'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.DefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.DefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_DefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.DefinitionStages.WithAttach'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.DefinitionStages.WithAttach.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_DefinitionStages_WithAttach'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.DefinitionStages.WithCondition'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.DefinitionStages.WithCondition.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_DefinitionStages_WithCondition'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.DefinitionStages.WithMetricName'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.DefinitionStages.WithMetricName.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_DefinitionStages_WithMetricName'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.DefinitionStages.WithScaleAction'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.DefinitionStages.WithScaleAction.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_DefinitionStages_WithScaleAction'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.DefinitionStages.WithStatistic'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.DefinitionStages.WithStatistic.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_DefinitionStages_WithStatistic'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.ParentUpdateDefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.ParentUpdateDefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_ParentUpdateDefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.ParentUpdateDefinitionStages.WithAttach'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.ParentUpdateDefinitionStages.WithAttach.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_ParentUpdateDefinitionStages_WithAttach'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.ParentUpdateDefinitionStages.WithCondition'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.ParentUpdateDefinitionStages.WithCondition.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_ParentUpdateDefinitionStages_WithCondition'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.ParentUpdateDefinitionStages.WithMetricName'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.ParentUpdateDefinitionStages.WithMetricName.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_ParentUpdateDefinitionStages_WithMetricName'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.ParentUpdateDefinitionStages.WithScaleAction'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.ParentUpdateDefinitionStages.WithScaleAction.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_ParentUpdateDefinitionStages_WithScaleAction'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.ParentUpdateDefinitionStages.WithStatistic'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.ParentUpdateDefinitionStages.WithStatistic.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_ParentUpdateDefinitionStages_WithStatistic'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.UpdateDefinitionStages.Blank'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.UpdateDefinitionStages.Blank.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_UpdateDefinitionStages_Blank'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.UpdateDefinitionStages.WithAttach'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.UpdateDefinitionStages.WithAttach.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_UpdateDefinitionStages_WithAttach'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.UpdateDefinitionStages.WithCondition'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.UpdateDefinitionStages.WithCondition.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_UpdateDefinitionStages_WithCondition'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.UpdateDefinitionStages.WithMetricName'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.UpdateDefinitionStages.WithMetricName.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_UpdateDefinitionStages_WithMetricName'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.UpdateDefinitionStages.WithScaleAction'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.UpdateDefinitionStages.WithScaleAction.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_UpdateDefinitionStages_WithScaleAction'.
[Warning-InvalidBookmark] Invalid link: 'ScaleRule.UpdateDefinitionStages.WithStatistic'. The file docs-ref-autogen/com.microsoft.azure.management.monitor.ScaleRule.UpdateDefinitionStages.WithStatistic.yml doesn't contain a bookmark named 'com_microsoft_azure_management_monitor_ScaleRule_UpdateDefinitionStages_WithStatistic'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

repo: Azure/azure-docs-sdk-java


text:
npm install fails

Running npm install on a clone of the 0.0.9 release fails with the following error:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: file-loader@1.1.11
npm ERR! Found: webpack@5.72.0
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"^5.72.0" from the root project
npm ERR!   peer webpack@"4.x.x || 5.x.x" from @webpack-cli/configtest@1.1.1
npm ERR!   node_modules/@webpack-cli/configtest
npm ERR!     @webpack-cli/configtest@"^1.1.1" from webpack-cli@4.9.2
npm ERR!     node_modules/webpack-cli
npm ERR!       dev webpack-cli@"^4.9.2" from the root project
npm ERR!       3 more (@webpack-cli/configtest, @webpack-cli/info, @webpack-cli/serve)
npm ERR!   6 more (css-loader, terser-webpack-plugin, webpack-cli, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^2.0.0 || ^3.0.0 || ^4.0.0" from file-loader@1.1.11
npm ERR! node_modules/file-loader
npm ERR!   dev file-loader@"^1.1.11" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: webpack@4.46.0
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"^2.0.0 || ^3.0.0 || ^4.0.0" from file-loader@1.1.11
npm ERR!   node_modules/file-loader
npm ERR!     dev file-loader@"^1.1.11" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

eresolve-report.txt
Technical info:

Node v18.12.1
npm 8.12.1
Microsoft Windows 10 Enterprise (10.0.19044 Build 19044)

Notes
Running npm i --legacy-peer-deps seems to work, albeit with 21 vulnerabilities (6 moderate, 13 high, 2 critical)

updated few dependencies and fixed in PR Defect/update dev dependencies by tanmaya-panda1 · Pull Request #58 · Azure/azure-kusto-trender (github.com)

source: gharchive/issue

repo: Azure/azure-kusto-trender

license: MIT

license_type: permissive

license_source: github-api


text:
Publish to npm?

Will this package be installable from npm?

Hello Joe,
Yes, we absolutely will be publishing this package tp npmjs.org, so that it is installable via npm

Is there a different tracking issue to publish to NPM?  That we can link to here?

No - any more than there is a tracking issue to publish for Node or .NET - it's just a part of the regular release cycle.

I guess I don't follow, isn't there work involved to make this consumable via npm (at least new artifacts), not to mention pulling in the localization logic into here so the built file is identical to the one on the CDN and  the copy published on NPM for Cordova?
I have tracking issues for CocoaPods/etc on iOS, so I'd expect the same here.

Good point - I will add a task specifically for that.

authors: adrianhall joewood phvannor

repo: Azure/azure-mobile-apps-js-client

license_source: bigquery


text:
Update bms.json

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

Hi @lapradh, Can you provide more info for why have this change, as it looks cause breaking change in stable version which is not allown.  understand healthDetails is renamed, but seems healthstatus remove enum value, it may a breaking change.

@changlong-liu to double confirm the swagger change which caused a sdk breaking change

/azp run automation - sdk

/azp run automation - sdk

Not sure why so many checks are in waiting status. Is there any other change required from my side?

/azp run

according to discuss offline, it is kind of revert for #9711, so approved the breaking for this PR, will request another SDK release again as sdk release on 5 Jun is wrong.

source: gharchive/pull-request

authors: AutorestCI akning-ms azuresdkci lapradh

repo: Azure/azure-rest-api-specs


text:
Fixing path in BackupAADProperties

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Fixing path for one API in 2018-12-20 vesion. No SDK has been generated on top of the existing version. Only python SDK 0.10.0 has the broken API and this SDK will be recalled. https://pypi.org/project/azure-mgmt-recoveryservicesbackup/0.10.0/

Hi @pratimaupadhyay02, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review.
Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ma/swaggerfeedback.

@pratimaupadhyay02 , please take above Action for breaking change review. Or this change can be taken with new api version.


text:
[NetAppFiles] Update netapp 2023 07 01 preview

ARM (Control Plane) API Specification Update Pull Request
Moves https://github.com/Azure/azure-rest-api-specs-pr/pull/17121  to public

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

[!NOTE]
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Click here to see the details of Step 1, Breaking Changes review
If you are in purview of Step 1 of the diagram, follow the Breaking Changes review process.
IMPORTANT! This applies even if you believe your PR was mislabeled, for any reason, including tool failure.

Click here to see the details of Step 2, ARM review
See https://aka.ms/azsdk/pr-arm-review.

 Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[x] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with PR workflow diagram Step 2 (ARM review), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Moves the changes in https://github.com/Azure/azure-rest-api-specs-pr/pull/17121   to public


text:
Add spec for alert repair/remediate

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: sumitabarahmand sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-java

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-node

@bganapa  @deathly809

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

@sarangan12 This is going thru azure stack admin api review board, please wait for sign off from @deathly809  or @bganapa  before merge

@sumitabarahmand The semantic validator is failing. Please fix it.

@sumitabarahmand Are you planning to take this in for the upcoming AZURESTACK release?

@shahabhijeet this should be good to merge

@shahabhijeet @sarangan12 , can one of you merge this pls, we had to update the SDK PR once this is merged.. Thanks!
https://github.com/Azure/azure-sdk-for-net/pull/5000

authors: AutorestCI azuresdkci bganapa msftclas sarangan12 sumitabarahmand


text:
add compute 2019-03-01 to Go SDK

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Can one of the admins verify this patch?

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/5766
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/5766/commits/3343c953cb23528556ac4d0c84b925d4905b0089

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java

@AutorestCI regenerate azure-sdk-for-go

authors: AutorestCI adxsdknet azuresdkci jhendrixMSFT


text:
[Hub Generated] Review request for Microsoft.DevTestLab to add version stable/2018-09-15

If you are a MSFT employee you can view your work branch via this link.
Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java

authors: AutorestCI azuresdkci joerage


text:
Make installing the guest agent configurable for VMImages

I know this would probably go into an option struct, but I think that should be another refactor. So for now just added a bool.
And while touching this file I also made it’s 100+ lines a little shorter which makes reviewing on GH a lot nicer.

Thanks! Tests are failing.

Argh, sorry about that! Tests updated now as well...

LGTM, @paulmey please review and merge.

LGTMToo

authors: ahmetalpbalkan paulmey svanharmelen

repo: Azure/azure-sdk-for-go


text:
v17.3.1

Thanks you for your contribution to the Azure-SDK-for-Go! We will triage and review it as quickly as we can.
As part of your submission, please make sure that you can make the following assertions:

[ ] I'm not making changes to Auto-Generated files which will just get erased next time there's a release.

If that's what you want to do, consider making a contribution here: https://github.com/Azure/autorest.go

[ ] I've tested my changes, adding unit tests where applicable.
[ ] I've added Apache 2.0 Headers to the top of any new source files.
[ ] I'm submitting this PR to the dev branch, or I'm fixing a bug that warrants its own release and I'm targeting the master branch.
[ ] If I'm targeting the master branch, I've also added a note to CHANGELOG.md.
[ ] I've mentioned any relevant open issues in this PR, making clear the context for the contribution.

Can one of the admins verify this patch?

@jhendrixMSFT can we pick up the latest containerservice spec too? Thanks!

@joshgav I'll do a full minor update early next week.

Okay thanks. Can you pick up the updated README from https://github.com/Azure/azure-sdk-for-go/commit/b9f76dbde4ccc31ebee29b1a2974885a613f8f87?

authors: azuresdkci jhendrixMSFT joshgav


text:
[Release] sdk/resourcemanager/workloadssapvirtualinstance/armworkloadssapvirtualinstance/0.1.0

https://github.com/Azure/sdk-release-request/issues/4843

The release request is held on.

/azp prepare-pipelines

/azp run prepare-pipelines

/azp run go - armworkloadssapvirtualinstance - ci

/azp run go - armworkloadssapvirtualinstance - ci

/azp run

/azp list

/azp run go - armworkloadssapvirtualinstance - ci

/azp run prepare-pipelines

/azp run go - armworkloadssapvirtualinstance - ci

Hi @benbp, /azp run go - armworkloadssapvirtualinstance - ci does not work properly, how do I use it.

/azp run go - armworkloadssapvirtualinstance - ci

/azp run prepare-pipelines

/azp run go - armworkloadssapvirtualinstance - ci

/azp run prepare-pipelines

/azp run go - armworkloadssapvirtualinstance - ci

/check-enforcer override


text:
[azblob] Pageblob documentation fix

[x] The purpose of this PR is explained in this or a referenced issue.
[x] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[x] Tests are included and/or updated for code changes.
[] Updates to module CHANGELOG.md are included.
[x] MIT license headers are included in each file.

/azp run go - azblob


text:
Automatic provider registration

When a subscription first access a namespace, the user will get an error similar to:
INFO: <-- 409 Conflict https://management.chinacloudapi.cn/subscriptions/23a32706-03c1-4920-a6ac-1b7c8de24bb4/resourceGroups/rgnems2ff173895519e/providers/Microsoft.Storage/storageAccounts/stg741191c6800ce?api-version=2016-01-01 (239ms, 205-byte body)
The subscription is not registered to use namespace 'Microsoft.Storage'. See https://aka.ms/rps-not-found for how to register subscriptions.

We should be able to plug in an interceptor that automatically handles the registration when this error occurs.

already implemented

authors: jianghaolu martinsawicki

repo: Azure/azure-sdk-for-java


text:
[Service Bus] setAutoDeleteOnIdle is not working for subscription a topic

@johnwickfootball commented on Fri May 21 2021
After sitting up setAutoDeleteOnIdle for 7mins the subscription is not getting delete. I am using Java with Azure service bus version 7.0.2
 SubscriptionDescription  sub = ManagementClient.createSubscription(topicName, subName);
 sub.setAutoDeleteOnIdle(duration(7mins);
 ManagementClient.updateSubcribeption(sub);

@jsquire commented on Sat May 22 2021
Hi @johnwickfootball.  Thanks for reaching out and we regret that you're experiencing difficulties.   I'm going to transfer this over to the Java SDK repository, as the folks there would be better able to assist.

@YijunXieMS could you help @johnwickfootball on this issue?

@ki1729 Please see if you can reproduce this issue. If so, then we can work with the service team to see what is wrong. You can also check with our friends from other languages to see if this a problem with our assumption or the service itself

Hi @ramya-rao-a ,
I'm from java sdk team. I tried to reproduce this bug in version 7.0.2 and latest version. And it works well. Have service team fixed this bug already?

@ZejiaJiang Looks like you used the azure-messaging-servicebus package which does not have a class called SubscriptionDescription. This class is in the older azure-servicebus package. Can you try reproducing the issue in the older one? If it works there as well, then we can close the issue

@ramya-rao-a ok, I'll try older version today.
I tried this version. Do you know the certain version?
<dependency>
        <groupId>com.azure</groupId>
         <artifactId>azure-messaging-servicebus</artifactId>
         <version>7.0.2</version>
</dependency>

@ZejiaJiang, I meant an older SDK: https://mvnrepository.com/artifact/com.microsoft.azure/azure-servicebus

@ZejiaJiang, I meant an older SDK: https://mvnrepository.com/artifact/com.microsoft.azure/azure-servicebus

I got it. Thank you.

Hi @ramya-rao-a ,
I checked the changelog of package azure-messaging-servicebus , only azure-messaging-servicebus:7.0.0-beta.4 support SubscriptionDescription and createSubscription .I tested this package and it works.
And then I tested azure-servicebus:3.6.6 azure-servicebus:3.6.0 and  azure-servicebus:3.5.1. All of them work as well.
Do I need more test of  azure-servicebus or we can close this issue?

That is good enough, thanks @ZejiaJiang
@johnwickfootball, if you still see this issue, please drop a comment with more details

authors: ZejiaJiang joshfree jsquire ramya-rao-a


text:
Microsoft Azure Service Bus - Session closed when producing messages

Query/Question
Dear,
Our application needs to send many(10k+) messages to a queue, we implement an outbox pattern, several records are updated to the pending state and a job reads these records and sends them to a queue. For performance, we split these records into a batch packet of 25 messages, send to the queue using the jmsTemplate(transacted) producer callback, for every batch a commit or rollback session is called. We are facing a problem, some messages were lost and we received warning messages saying “The session is closed”. This warning appears for the producer thread but appears for random @JmsListeners consumers too. Due to warning message and not a exception we update registers like ok in database but acctualy some messages are lost.
We are unable to reproduce locally and this issue occurs intermittently in our environment. We have 24 @JMSlistener consumers and 2 jobs for sending messages.
We think its related to https://github.com/Azure/azure-sdk-for-java/issues/37042.
Could you help us please?
Producer stack:
Caught exception trying rollback() when putting session back into the pool, will invalidate. jakarta.jms.IllegalStateException: The Session is closed
jakarta.jms.IllegalStateException: The Session is closed
	at org.apache.qpid.jms.JmsSession.checkClosed(JmsSession.java:1113)
	at org.apache.qpid.jms.JmsSession.rollback(JmsSession.java:264)
	at org.messaginghub.pooled.jms.JmsPoolSession.close(JmsPoolSession.java:112)
	at org.springframework.jms.support.JmsUtils.closeSession(JmsUtils.java:109)
	at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:513)
	at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:534)
	at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:526)
	at br.com.a.a.t.integration.usecase.integration.adapter.external.job.SendToOffTradeJobBase.enqueue(SendToOffTradeJobBase.java:84)
	at br.com.a.a.t.integration.usecase.integration.adapter.external.job.SendToOffTradeJobBase.updateStatusAndEnqueue(SendToOffTradeJobBase.java:77)
	at br.com.a.a.t.integration.usecase.integration.adapter.external.job.SendToOffTradeJobBase.prepareAndSend(SendToOffTradeJobBase.java:71)
	at br.com.a.a.t.integration.usecase.integration.adapter.external.job.SendToOffTradeJobBase.execute(SendToOffTradeJobBase.java:57)
	at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
	at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)

@JmsListener stack
Setup of JMS message listener invoker failed for destination 'queue-name' - trying to recover. Cause: The Session is closed
Caught exception trying rollback() when putting session back into the pool, will invalidate. jakarta.jms.IllegalStateException: The Session is closed
jakarta.jms.IllegalStateException: The Session is closed
	at org.apache.qpid.jms.JmsSession.checkClosed(JmsSession.java:1113)
	at org.apache.qpid.jms.JmsSession.rollback(JmsSession.java:264)
	at org.messaginghub.pooled.jms.JmsPoolSession.close(JmsPoolSession.java:112)
	at org.springframework.jms.support.JmsUtils.closeSession(JmsUtils.java:109)
	at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.clearResources(DefaultMessageListenerContainer.java:1291)
	at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1137)
	at java.base/java.lang.Thread.run(Thread.java:831)

Pool configuration:
spring.jms.servicebus.idle-timeout=30000
spring.jms.servicebus.pool.enabled=true
spring.jms.servicebus.pool.max-connections=10
spring.jms.servicebus.pool.time-between-expiration-check=10000
spring.jms.servicebus.pool.idle-timeout=60000

JmsTemplate producer:
public void enqueue(List<StimulusConsolidation> stimulusConsolidationList) {
        jmsTemplate.setSessionTransacted(true);
        jmsTemplate.execute(getMessageProducerCallback(stimulusConsolidationList));
    }

    public ProducerCallback<Message> getMessageProducerCallback(List<StimulusConsolidation> stimulusConsolidationList) {
        return (session, producer) -> {
            Queue queue = session.createQueue(getQueueName());
            try {
                for (StimulusConsolidation e : stimulusConsolidationList) {
                    producer.send(queue, appMessageConverter.toMessage(e, session));
                }
                session.commit();
            } catch (Exception e) {
                session.rollback();
                throw e;
            }
            return null;
        };
    }

Setup (please complete the following information if applicable):

OS: Linux Docker image on AKS.
OpenJDK 17
SpringBoot 3.1.5
Library/Libraries: [spring-cloud-azure-starter-servicebus-jms (groupId:com.azure.spring:5.3.0)]
Service Bus Tier: Standard

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x ] Query Added
[x ] Setup information Added

had the same or a similar issue - we fixed it by setting "partitioning" to false and enabled "dead lettering on message expiration" for all queues

Hi @Andrexams  , thanks for reaching out.
We have received your submission and will take it into consideration. We appreciate your input and will review this matter as soon as possible.
Please feel free to provide any additional information or context that you think may be helpful. We'll keep you updated on the progress of our review.
Thank you for your contribution to improving our project.

Hi @Andrexams , ServiceBus server side has a fix recently for premium tier.
So if you still meet this error in premium tier, please add environment property PN_TRACE_FRM=1 and provide the log info here, thanks.

authors: Andrexams Netyyyy neffsvg


text:
Communication Resource | API Version Update

Description
Live test pipelines are failing due to the failure of deployment test resources in INT environment for all the modalities across all the platforms since the Communication Services API version : 2020-08-20-preview is obsolete, which was recently removed from support.
Updating API version to 2023-03-31.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run java - azure-communication-identity - tests


text:
Fix CVE-2023-25194

Description
Fix CVE-2023-25194
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
spring-cloud-azure-service

close it for already fix

authors: Netyyyy azure-sdk


text:
Trande query methods no criteria bug - just change log

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

Abandoning or PR #40206.

API change check
API changes are not detected in this pull request.


text:
Express being brought in a dependency

We are getting an error webpacking with the latest @azure/identity release, 1.2.0. It is dependent upon express. If it is not already included you get an error "Module not found: Error: Can't resolve 'express' in '...\node_modules@azure\identity\dist-esm\src\credentials'". If you include it the overall built artefact size gets increased by +10MB!!! We are using this to build serverless artefacts, e.g. Azure Function Apps so this has a huge impact on us.
Express is referenced in interactiveBrowserCredential.ts.
This was brought in by the commit https://github.com/Azure/azure-sdk-for-js/commit/cce70bb22861b2f0dc5f7a80bf1895d10748a39c.
It is even referenced in the package.json as a development dependency. Can this be removed in the future as this significantly impacts built artefacts.

Thanks for the feedback. I've filed https://github.com/Azure/azure-sdk-for-js/issues/13465 to track a few ways we can address this issue.

Thanks for the feedback. I've filed https://github.com/Azure/azure-sdk-for-js/issues/13465 to track a few ways we can address this issue.

Update: We have removed the dependency on express in https://github.com/Azure/azure-sdk-for-js/pull/14521 and the version 1.2.5 of the @azure/identity package has these changes
Thanks for reporting @chattersley!

authors: chattersley jonathandturner ramya-rao-a

repo: Azure/azure-sdk-for-js


text:
Dependency package @typescript-eslint/parser has a new version available

We have identified a dependency on version 4.19.0 of @typescript-eslint/parser. A new version (5.24.0) is available for upgrade.
Following are the steps to upgrade package dependency.

Understand the breaking changes between the version being used and the version you want to upgrade to.

Identify all packages that take a dependency on this package.

Go to the root folder for each such package (/sdk/service-name/package-name) and update package.json to have the new version.

Run rush update to ensure the new version is pulled in.

Make relevant changes to absorb the breaking changes.

Repeat steps 3 to 5 for each of the packages that have a dependency on this package.

Pre-requisite to updating this package is updating eslint to v8 i.e. #19219

upgrade to ~5.22.0 in PR #21733

authors: azure-sdk jeremymeng ramya-rao-a


text:
Tracking SSO Investigation (2024 edition)

Previous issue: https://github.com/Azure/azure-sdk-for-js/issues/22904 (closed for inactivity, a new one must be open)
VisualStudioCodeCredential will depend on a new authentication tool which replaces the Azure Account extension in Visual Studio Code. This tool is not yet built; more details to come.

See https://github.com/Azure/azure-sdk-for-js/issues/22904

I think this can be closed and new issues can be filed once https://github.com/Azure/azure-sdk-for-net/issues/30525 / https://github.com/microsoft/vscode/issues/178740 is resolved

authors: joshfree maorleger


text:
[core-http] cancelledrequests throw request_aborted_error instead of AbortError.

Related to #3601
In core-http, it appears that when a request is aborted, we throw a RestError where the code is REQUEST_ABORTED_ERROR.
Example of error being thrown:
https://github.com/Azure/azure-sdk-for-js/blob/425d5f02f37c42d9154dcb4be8cc9b0bb0f257f4/sdk/core/core-http/lib/fetchHttpClient.ts#L45-L52
Value of REQUEST_ABORTED_ERROR:
https://github.com/Azure/azure-sdk-for-js/blob/425d5f02f37c42d9154dcb4be8cc9b0bb0f257f4/sdk/core/core-http/lib/restError.ts#L9
I have 2 questions from this:

Do we need to return a RestError when a request is aborted? Aside from the httpRequest, there won't be a body/response/statusCode to assign to the error. Instead, should we throw an AbortError (we could even add request to the AbortError if we need).

If we do need to keep throwing a RestError, should the code be changed to AbortError?

My vote would be to go with option 1 but if that's too wide-impacting a change (all core-http consumers) would option 2 suffice?
/cc @ramya-rao-a @bterlson

Throwing an AbortError (option #1) seems appropriate (and per guideliens) to me.

authors: bterlson chradek


text:
[MQ] Update KeyVault tests.yml and test-resources.json

For #6647

Fixed by #6557


text:
Fix Cosmos Samples

Fix issue #17930

Update ../../dist-sem to @azure/cosmos
Migrate samples to V2
Enable strict mode on samples
SDK update

Note : We need to publish the SDK as the samples uses some of the exports which are not in live yet. SasTokenAuth.ts

API changes have been detected in @azure/cosmos. You can review API changes here

/azp run js - cosmosdb - ci

/azp run js - cosmosdb - ci

API changes have been detected in @azure/cosmos. You can review API changes here

@sajeetharan I made a few changes.

Moved assets/Data/Families.json to samples-dev/Data/Families.json and changed the way it is imported (the usage pattern that was there previously wouldn't work with the JavaScript layout, only TypeScript). I changed the sample configuration in package.json as well, and added json files to the includes in the tsconfig.json.
Rewrote all x?.y in samples-dev to some form of x && x.y.
Ran experimental generator. It passes fine with the above changes.

/azp run js - cosmosdb - tests

authors: azure-sdk sajeetharan witemple-msft


text:
[do not merge] testing vitest error filtering ideas

Packages impacted by this PR
Issues associated with this PR
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.

authors: azure-sdk timovv


text:
[FEATURE REQ] Storage: Better Stream support

Hi Guys,
Using latest SDK: 12.4.4
We're migrating to the Azure and was a bit surprised the SDK does not have "full" Stream support.
Imagine we have following code that writes stream:
            using (var fileStream = fileProvider.CreateOutputStream(fullFilePath))
            using (var outputStream = new ZipOutputStream(fileStream))
            using (var writer = new StreamWriter(outputStream))
            {
                outputStream.PutNextEntry(new ZipEntry($"{reportTitle}.{FileExtensionConstant.CSV}"));
                new CommissionHistoryCsvExporter().ExportToCsv(selectQuery, queryParams, writer);
            }

In the code above, CreateOutputStream, creates file based stream.
With current API we cannot migrate to the Azure blob storage without significant code changes, currently to upload the blow there is only one method Upload that accepts stream that must "pre exists". In other words, you have to have a stream already, and in order to get one you must create it on the memory or file. Creating it on memory is not acceptable for us as files might be big, creating on the file system in not acceptable because of the load and space limitations.
Suggestions:
Add API to expose upload/download stream explicitly.
Like:

Stream .GetUploadStream()
Stream .GetDownloadStream()

This will fully enable Stream.CopyTo() functionality and will make integration with existing code way simpler.
Seems similar issues:
https://github.com/Azure/azure-sdk-for-net/issues/9607

@seanmcc-msft  is this a duplicate?

Just FYI, in the V11 there is OpenWrite method that does exactly what we need.

Duplicate of https://github.com/Azure/azure-sdk-for-net/issues/9607.
We are actively working on this issue: https://github.com/Azure/azure-sdk-for-net/pull/12400, https://github.com/Azure/azure-sdk-for-net/pull/13344.

authors: amnguye seanmcc-msft yahorsi

repo: Azure/azure-sdk-for-net


text:
[Flaky Test] Azure.Monitor.OpenTelemetry.Exporter.Tests.AzureMonitorExporterEventSourceTests.VerifyEventSource_Error_WithAggregateException

https://dev.azure.com/azure-sdk/public/_build/results?buildId=1622893&view=ms.vss-test-web.build-test-results-tab&runId=32288564&resultId=115491&paneView=debug

Label prediction was below confidence level 0.6 for Model:CategoryLabels: 'Mgmt:0.5557361,Client:0.40559825,Service:0.033468973'

/cc @TimothyMothra

@JoshLove-msft this should be resolved now.
Please let me know if you see any more issues.
Thanks!

@JoshLove-msft this should be resolved now. Please let me know if you see any more issues.
Thanks!

Thank you for the quick fix!

authors: JoshLove-msft TimothyMothra azure-sdk


text:
Get access token using Microsoft.Azure.Services.AppAuthentication in a container

I've got a docker container using the AzureServiceTokenProvider to get an access token to access key vault but it's not working. I'm getting the following exception message:
Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/{GUID}. Exception Message: Tried the following 3 methods to get an access token, but none of them worked.
Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/{GUID}. Exception Message: Tried to get token using Managed Service Identity. Unable to connect to the Managed Service Identity (MSI) endpoint. Please check that you are running on an Azure resource that has MSI setup.
Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/{GUID}. Exception Message: Tried to get token using Visual Studio. Access token could not be acquired. Environment variable LOCALAPPDATA not set.
Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/{GUID}. Exception Message: Tried to get token using Azure CLI. Access token could not be acquired.

I'm not sure if the nuget package should be working inside a docker container I start up using Visual Studio (docker-compose).

Anyone have an idea if this should be working or if this is not supported currently?

@Zenuka please give a test drive for this cli tool https://www.nuget.org/packages/appauthnetication/#

To use the app auth library in a container on local machine, you will need to set env variables to use an explicit service principal credential. https://docs.microsoft.com/en-us/azure/key-vault/service-to-service-authentication#running-the-application-using-a-service-principal

authors: Zenuka kdcllc varunsh-msft


text:
[BUG] Updating NotificationHub GCM/FCM Credentials

Describe the bug
When using NotificationHubsManagementClient.NotificationHubs.CreateOrUpdate() to change the GCM/FCM credentials for a Notification Hub, the credentials do not change.
To Reproduce

Create a new notification hub, assigning it a GCM/FCM key.
Use NotificationHubsManagementClient.NotificationHubs.CreateOrUpdate() to update the hub with a new GCM/FCM key.

Code Snippet
using Microsoft.Azure.Management.NotificationHubs;
using Microsoft.Azure.Management.NotificationHubs.Models;
using Microsoft.IdentityModel.Clients.ActiveDirectory;
using Microsoft.Rest;

namespace AzureTesting
{
  internal class NotificationHubtTest
  {
    const string SUBSCRIPTION_ID = "My Subscription ID";

    const string RESOURCE_GROUP = "Default-NotificationHubs-CentralUS";
    const string HUB_NAME = "DefaultHub";
    const string HUB_LOCATION = "Central US";

    // These constants are required for authenticating my app in the Azure AD.
    const string TENANT_ID = "My Tenant ID";
    const string CLIENT_ID = "My Client ID";
    const string CLIENT_SECRET = "My Client Secret";

    public void Test()
    {
      string namespaceName = "MyNotificationHubNamespace";

      // Create a new notification hub for my notification hub namespace.
      CreateOrUpdateHub(namespaceName, "My First Key");

      // Wait a little bit to ensure the hub is created.
      // (Not normally how I would do this, but this is for demonstration purposes.)
      System.Threading.Thread.Sleep(10000);

      // If I look at the new hub on portal.azure.com, it has the correct GCM/FCM key assigned.

      // Now update the hub with a new GCM/FCM key.
      CreateOrUpdateHub(namespaceName, "My Second Key");

      // When check on the hub at this point on portal.azure.com, it still has
      // the old GCM/FCM key ("My First Key") and not the new one ("My Second Key").
    }

    private NotificationHubResource CreateOrUpdateHub(string namespaceName, string gcmKey)
    {
      var parameters = new NotificationHubCreateOrUpdateParameters()
      {
        NotificationHubCreateOrUpdateParametersName = HUB_NAME,
        Location = HUB_LOCATION,
        GcmCredential = new GcmCredential(null, gcmKey)
      };

      using (var client = CreateClient())
      {
        var hub = client.NotificationHubs.CreateOrUpdate(RESOURCE_GROUP, namespaceName, HUB_NAME, parameters);
        return hub;
      }
    }

    private NotificationHubsManagementClient CreateClient()
    {
      var credentials = GetClientCredentials(TENANT_ID, CLIENT_ID, CLIENT_SECRET);
      var client = new NotificationHubsManagementClient(credentials);
      client.SubscriptionId = SUBSCRIPTION_ID;
      return client;
    }

    private TokenCredentials GetClientCredentials(string tenantID, string clientID, string clientSecret)
    {
      var context = new AuthenticationContext($"https://login.microsoftonline.com/{tenantID}");
      var result = context.AcquireTokenAsync("https://management.core.windows.net/", new ClientCredential(clientID, clientSecret)).Result;
      var credentials = new TokenCredentials(result.AccessToken);

      return credentials;
    }
  }
}

Expected behavior
The GCM/FCM credentials should change to reflect what was set in the NotificationHubCreateOrUpdateParameters class.
Setup (please complete the following information):

OS: Windows 10 Pro (Build 17763)
IDE : Visual Studio Professional 2017
Microsoft.Azure.Management.NotificationHubs v2.3.2 (preview)
.NET Framework: 4.7.2
Language: C#

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[x] Setup information Added

Thank you for opening this issue! We are routing it to the appropriate team for follow up.

Sorry for late response; Thejaswini could you share some insights on this, thanks?

Closing due to no repro

authors: iganderson isra-fel kurtzeborn stankovski


text:
Allow customers to parse certificate, key, and secret IDs from URLs

We had an internal customer request to allow customers to pass a URI to methods instead of just a name, since, for example, customers can copy the URI from the portal and wouldn't otherwise have to parse the name out themselves.
Things to consider,

Do we provide method overloads to take a Uri, or just expose (through abstraction, perhaps) our existing internal APIs that parse it for them?
If the methods to take a full Uri, do we assert that it has the same base Uri for which the client class was instantiated?

@heaths, perhaps this could be solved by making KeyVaultIdentitifier public to allow people to parse the Id? I agree it's a bit more awkward than just having the method take a uri.
The other possibility is we could create classes similar to the KeyResolver, which is vault agnostic, for Secrets and Certificates.

+1 on the idea of a KeyResolve-like helper.

Yeah, the resolver helper can work.
But its implementation details are not quite straight,
as with Key Resolver we have the Crypto client tied to a Key.
In Secret, Key and Certificate cases clients are tied to vault.
We will need to validate that key vault identifers are of the vault to which client is configured for too.

Note: based on guidelines, we should also provide a throwing variant of the TryParse method.

authors: g2vinay heaths schaabs


text:
Fixed race condition: small block parallel upload

Seems to fix a race condition in block blob parallel uploads when blocks
are extremely small (1 KB). Need to continue watching for flakey tests
outlined in https://github.com/Azure/azure-sdk-for-net/issues/13221.

/azp run net - storage - ci

@kasobol-msft

authors: jaschrep-msft seanmcc-msft


text:
Adding WebPubSub Client Library

Adding a new client library for the Azure Web PubSub Service.

/azp run prepare-pipelines

/azp run prepare-pipelines

authors: KrzysztofCwalina pakrym


text:
refactor(resourcemanager): remove virtual call in ArmResource constructor

remove virtual from all ValidateResourceType methods
extract common property initialization logic into ArmResource.Initialize
for all classes inheriting ArmResource, change the constrctor implemenation to not rely on base class initialization, so that we can invoke local version of ValidateResourceType in the costructors.

resolve #1627
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

Before we start to change autorest.csharp, let's discuss the target codes we want. Personally, I think we'd better keep current behavior.
I think we don't have a good solution here. What we want is to:

enforce validation during object construction
make sure validation logic can be overwritten

The problem is that virtual calls in constructor is normally considered not good. If we choose to eliminate this virtual call, we can:

make those ValidateResourceType methods private, and invoke them in their own class constructors. But that actually changes the behavior that the ValidateResourceType is not overwritten. Instead, each level of class will have its own check.

[update]: This solution is not feasible, because the base class ValidateResourceType logic is not suitable for child class. An example is GenericResourceCollection, it won't pass the validation in ArmResource.

make those ValidateResourceType methods private, but constructors of each level of class will not invoke the non-default base constructor. Instead, they repeat the same logic of base constructors, and invoke the its own ValidateResourceType. This is kind of rigid, create duplicated codes, and is not easy to maintain this pattern in the future.

On the other hand, ValidateResourceType is OK here. See the reference doc about how csharp does in constructors.
constructor()
{
    auto generated: initialize the member variables (fields) of this class
    auto generated: call the base class constructor (if we have a base class)
    [your constructor code here]
}

The properties of each class is initialized, before the base class constructor is invoked. As long as we keep it simple, virtual calls in this case should be fine.

close this PR, since we've made decision to keep the existing codes in debug model.


text:
[Cdn] Address follow up review comments

This PR implements following changes:

Changed the type of ProvisioningState in cdn.json from string to extensible enum
Changed the type of Unit in ResourceUsage from string to extensible enum

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check for Azure.ResourceManager.Cdn
API changes have been detected in Azure.ResourceManager.Cdn. You can review API changes here

Still one comment in Cdn need to be resolved.


text:
Update Azure.Core shared for LRO rehydration

Construct RehydrationToken from multiple fields

HeaderSource: Indicates where the NextRequestUri locates in the initial response header, it could be OperationLocation, AzureAsyncOperation, Location or None
NextRequestUri: The Uri to poll status of the operation
InitialUri: The initial Uri of the operation
RequestMethod: Http request method of the operation
LastKnowLocation: The last known Location value in the response header
FinalStateVia: Configuration from API spec, it could be AzureAsyncOperation, Location, OriginalUri or OperationLocation

For fake delete LRO with 404, just return empty response with 204 because the delete succeeded
To support LRO rehydration for both DPG and MPG, make Operation non-abstract

API change check
API changes are not detected in this pull request.

Pending on https://github.com/Azure/azure-sdk-for-net/pull/41655

Can we eliminate some of the shared source files? We consider shared sources to be engineering debt.

Removed the share core files.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Security.KeyVault.Certificates Azure.Security.KeyVault.Keys Azure.Security.KeyVault.Secrets Azure.AI.TextAnalytics Azure.AI.Translation.Document Azure.AI.FormRecognizer Azure.Communication.Email Azure.Core Azure.Core.Experimental Azure.Security.ConfidentialLedger Azure.AI.Translation.Text Azure.Communication.JobRouter Azure.Communication.CallAutomation Azure.Communication.CallingServer Azure.Communication.Chat Azure.Communication.Messages Azure.Communication.Sms Azure.Communication.Rooms Azure.Communication.Identity Azure.Communication.MediaComposition Azure.Communication.NetworkTraversal Azure.Communication.PhoneNumbers Azure.Communication.ShortCodes Azure.Communication.AlphaIds Azure.Data.Tables Azure.Template Azure.IoT.TimeSeriesInsights Azure.AI.Vision.ImageAnalysis Azure.Media.VideoAnalyzer.Edge Azure.Messaging.WebPubSub Azure.Messaging.WebPubSub.Client Azure.Security.KeyVault.Administration

All the changes are reverted, no file changes to refresh the APIView.

I left a couple of minor nits, nothing that I'd consider blocking.
@m-nash:  Would you please own the final review for approval?   I'm not familiar enough with the design to feel comfortable doing so.

continue the work in https://github.com/Azure/azure-sdk-for-net/pull/42686

authors: azure-sdk jsquire live1206


text:
Rename PackageProj ReadMe

Switch from pointing to commitSha to pointing to master

/azp run net - client


text:
Search Documents Readme and Samples issues

Section link:

Suggestion:
Update client to search_client.

Section link1, link2:

Suggestion:
Add await before code client.delete_data_source_connection("async-sample-data-source-connection")

Section link:

Suggestion:
Update indexer-datasource to async-indexer-datasource，make it consistent with the data source name below.

Section link1, link2:

Reason:
AttributeError: 'NoneType' object has no attribute 'request'.
When using async with client, after the internal code execution of with ends, the __aexit__ method of the client object is automatically called, and the __aexit__ method calls the close() method of the client.
The client in the code is a global variable. After a functional function in the code uses with, the global client will be automatically closed, causing other functional functions to be unable to continue to use the client, causing an exception.
Suggestion:
Remove async with client:.
@jongio for notification.

Fixed in #13317

repo: Azure/azure-sdk-for-python


text:
Deployment Manager Content Validation Issue for github.io website

Section Link:

https://azuresdkdocs.blob.core.windows.net/$web/python/azure-mgmt-deploymentmanager/1.0.0/index.html

Reason:
Format validation Issue: Layout error, version tags and module tags overlap.

Section Link:

https://azuresdkdocs.blob.core.windows.net/$web/python/azure-mgmt-deploymentmanager/1.0.0/index.html

Reason:
Format validation Issue: Layout error, the expected results is shown below：

Section Links:

https://azuresdkdocs.blob.core.windows.net/$web/python/azure-mgmt-deploymentmanager/1.0.0/genindex.html
https://azuresdkdocs.blob.core.windows.net/$web/python/azure-mgmt-deploymentmanager/1.0.0/azure.mgmt.deploymentmanager.models.html

Reason:
Format validation Issue: Many text in this page exceed the page size.

Section Link:

https://azuresdkdocs.blob.core.windows.net/$web/python/azure-mgmt-deploymentmanager/1.0.0/azure.mgmt.deploymentmanager.operations.html

Reason:
Format validation Issue: Extra symbols ~ or -.

Section Link:

https://azuresdkdocs.blob.core.windows.net/$web/python/azure-mgmt-deploymentmanager/1.0.0/azure.mgmt.deploymentmanager.models.html

Reason:
Typing annotation Issue: Please unify the format, update to **kwargs:Any or **kwargs.

Section Link:

https://azuresdkdocs.blob.core.windows.net/$web/python/azure-mgmt-deploymentmanager/1.0.0/azure.mgmt.deploymentmanager.operations.html

Reason:
Typing annotation Issue: Please unify the format, update to *args:Any, **kwargs:Any or *args, **kwargs.
@rohit-ganguly , @lmazuel for notification.

Close this issue as we'll put it into a summarzied one.