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 da06e4db3383eab438b499be38696933e12e3b49 #4401

Conversation

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

This PR is automatically generated based on the commit da06e4d

Copy link

Breaking Changes

No Breaking Changes were found 👍

Copy link

Summary of Changes

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

Non-Breaking Changes

3 Non-Breaking Changes were detected:

  • New Service: Fabric.
  • New API Version: 2023-11-01 in Fabric.
  • New API Resource: FabricCapacities in Fabric@2023-11-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.Fabric
  • capacities
  • locations
  • providers
  • resourceGroups
  • subscriptions

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

Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🏖️

@katbyte katbyte merged commit 0698db4 into main Sep 10, 2024
3 checks passed
@katbyte katbyte deleted the data/regeneration-from-da06e4db3383eab438b499be38696933e12e3b49-rest-api-specs branch September 10, 2024 15:15
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