Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global ms.service and ms.subservice metadata update #3115

Merged
merged 1 commit into from
Aug 1, 2024

Conversation

mikefrobbins
Copy link
Contributor

PR Summary

Global ms.service and ms.subservice metadata update

PR Checklist

  • Descriptive Title: This PR's title is a synopsis of the changes it proposes.
  • Summary: This PR's summary describes the scope and intent of the change.
  • Contributor's Guide: I have read the contributors guide.
  • Style: This PR adheres to the style guide.

Copy link
Contributor

Learn Build status updates of commit 2845efe:

💡 Validation status: suggestions

File Status Preview URL Details
docfx.json 💡Suggestion Details

docfx.json

  • Line 158, Column 56: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: hdinsight' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-hdinsight'.
  • Line 170, Column 71: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: notification-hubs' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-notification-hubs'.
  • Line 175, Column 67: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: site-recovery' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-site-recovery'.
  • Line 176, Column 74: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: site-recovery' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-site-recovery'.
  • Line 178, Column 54: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: service-bus' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-service-bus'.
  • Line 179, Column 65: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: resource-graph' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-resource-graph'.
  • Line 181, Column 56: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: scheduler' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-scheduler'.
  • Line 184, Column 59: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: service-bus' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-service-bus'.
  • Line 185, Column 65: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: service-fabric' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-service-fabric'.
  • Line 186, Column 52: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: signalr' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-signalr-service'.
  • Line 187, Column 63: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: site-recovery' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-site-recovery'.
  • Line 190, Column 69: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: stream-analytics' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-stream-analytics'.
  • Line 192, Column 67: [Suggestion: value-deprecated-replace - See documentation] The 'ms.service: traffic-manager' you used is now deprecated and can no longer be used. We suggest you replace it with 'ms.service: azure-traffic-manager'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions 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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant