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

Data: Rest Api Specs - regenerating based on 410bb4f76763a1d832d8d0ecc8b924c6f8f08fda #3616

Conversation

hc-github-team-tf-azure
Copy link
Collaborator

This PR is automatically generated based on the commit 410bb4f

Copy link

Breaking Changes

No Breaking Changes were found 👍

Copy link

Summary of Changes

  • 👍 No Breaking Changes were detected.
  • 👀 5 Non-Breaking Changes were detected.

Non-Breaking Changes

5 Non-Breaking Changes were detected:

  • New API Version: 2021-07-01-preview in Insights.
  • New API Resource: PrivateEndpointConnections in Insights@2021-07-01-preview.
  • New API Resource: PrivateLinkResources in Insights@2021-07-01-preview.
  • New API Resource: PrivateLinkScopedResources in Insights@2021-07-01-preview.
  • New API Resource: PrivateLinkScopesAPIs in Insights@2021-07-01-preview.

Copy link

New Resource ID Segments containing Static Identifiers

The following new Static Identifiers were detected from the set of changes (new/updated Resource IDs).

Note: Resource ID segments should always be camelCased and not TitleCased, lowercased or kebab-cased.

Please review the following list of Static Identifiers:


  • Microsoft.Insights
  • privateEndpointConnections
  • privateLinkResources
  • privateLinkScopes
  • providers
  • resourceGroups
  • scopedResources
  • subscriptions

Note: Resource ID segments should always be camelCased and not TitleCased, lowercased or kebab-cased.

@tombuildsstuff tombuildsstuff merged commit b2acc82 into main Jan 12, 2024
3 checks passed
@tombuildsstuff tombuildsstuff deleted the data/regeneration-from-410bb4f76763a1d832d8d0ecc8b924c6f8f08fda-rest-api-specs branch January 12, 2024 11:00
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.

2 participants