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 f521a08772b46550d4be9b86f26f9ec4d3c41df6 #4523

Conversation

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

This PR is automatically generated based on the commit f521a08

Copy link

Breaking Changes

🛑 3 Breaking Changes were detected.


Summary of changes:

  • Field Now Optional: RemoteVolumeResourceId in Model ReplicationObject in NetApp@2024-07-01/SnapshotPolicyListVolumes.
  • Field Now Optional: RemoteVolumeResourceId in Model ReplicationObject in NetApp@2024-07-01/VolumeGroups.
  • Field Now Optional: RemoteVolumeResourceId in Model ReplicationObject in NetApp@2024-07-01/Volumes.

Copy link

Summary of Changes

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

Breaking Changes

3 Breaking Changes were detected:

  • Field Now Optional: RemoteVolumeResourceId in Model ReplicationObject in NetApp@2024-07-01/SnapshotPolicyListVolumes.
  • Field Now Optional: RemoteVolumeResourceId in Model ReplicationObject in NetApp@2024-07-01/VolumeGroups.
  • Field Now Optional: RemoteVolumeResourceId in Model ReplicationObject in NetApp@2024-07-01/Volumes.

Copy link

New Resource ID Segments containing Static Identifiers

No new Resource ID Segments containing Static Identifiers were identified in the set of changes 🤙.

@stephybun stephybun merged commit 0560468 into main Oct 29, 2024
3 checks passed
@stephybun stephybun deleted the data/regeneration-from-f521a08772b46550d4be9b86f26f9ec4d3c41df6-rest-api-specs branch October 29, 2024 09:16
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