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 71cccf637325e9f2fd7072a3663525138a07bcd7 #4404

Conversation

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

This PR is automatically generated based on the commit 71cccf6

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 Service: DevOpsInfrastructure.
  • New API Version: 2024-04-04-preview in DevOpsInfrastructure.
  • New API Resource: ImageVersions in DevOpsInfrastructure@2024-04-04-preview.
  • New API Resource: Pools in DevOpsInfrastructure@2024-04-04-preview.
  • New API Resource: ResourceDetails in DevOpsInfrastructure@2024-04-04-preview.
  • New API Resource: Sku in DevOpsInfrastructure@2024-04-04-preview.
  • New API Resource: SubscriptionUsages in DevOpsInfrastructure@2024-04-04-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.DevOpsInfrastructure
  • images
  • locations
  • pools
  • providers
  • resourceGroups
  • subscriptions

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

@katbyte katbyte closed this Sep 10, 2024
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