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 c5a452dfe253913e625673cefa99d60938651e3a #4364

Conversation

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

This PR is automatically generated based on the commit c5a452d

Copy link

Breaking Changes

No Breaking Changes were found 👍

Copy link

Summary of Changes

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

Non-Breaking Changes

7 Non-Breaking Changes were detected:

  • New API Version: 2024-07-01 in Resources.
  • New API Resource: DeploymentOperations in Resources@2024-07-01.
  • New API Resource: Deployments in Resources@2024-07-01.
  • New API Resource: Providers in Resources@2024-07-01.
  • New API Resource: ResourceGroups in Resources@2024-07-01.
  • New API Resource: Resources in Resources@2024-07-01.
  • New API Resource: Tags in Resources@2024-07-01.

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.Management
  • Microsoft.Resources
  • deployments
  • managementGroups
  • operations
  • providers
  • resourceGroups
  • subscriptions
  • tagNames
  • tagValues

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

@stephybun stephybun merged commit 8a2c8ce into main Aug 19, 2024
3 checks passed
@stephybun stephybun deleted the data/regeneration-from-c5a452dfe253913e625673cefa99d60938651e3a-rest-api-specs branch August 19, 2024 09:19
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