Added new property SegmentCount to SMSReceived Event #31764
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Generated ApiView
|
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
This was referenced Dec 4, 2024
grangasamy-msft
added
the
PublishToCustomers
grangasamy-msft
requested review from
lmazuel,
jsquire and
l0lawrence
as code owners
l0lawrence
reviewed
Dec 10, 2024
...zure.Messaging.EventGrid.SystemEvents/Microsoft.Communication/AzureCommunicationServices.tsp
Outdated
Show resolved
Hide resolved
...zure.Messaging.EventGrid.SystemEvents/Microsoft.Communication/AzureCommunicationServices.tsp
Outdated
Show resolved
Hide resolved
github-actions
bot
added
the
brownfield
...zure.Messaging.EventGrid.SystemEvents/Microsoft.Communication/AzureCommunicationServices.tsp
Outdated
Show resolved
Hide resolved
AzureRestAPISpecReview
added
the
BreakingChangeReviewRequired
microsoft-github-policy-service
bot
added
the
no-recent-activity
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Show resolved
Hide resolved
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
grangasamy-msft
force-pushed
the
grangasamy/SMSReceivedEvent
branch
from
38e818a to
5677019
Compare
|
Hello Josh, The json files are fixed. Can you please review and let me know. Thank you. |
grangasamy-msft
added
the
Versioning-Approved-BugFix
l0lawrence
reviewed
Jan 10, 2025
...ation/eventgrid/Azure.Messaging.EventGrid.SystemEvents/examples/2018-01-01/sms_received.json
Show resolved
Hide resolved
...cation/eventgrid/data-plane/Microsoft.EventGrid/stable/2024-01-01/GeneratedSystemEvents.json
Outdated
Show resolved
Hide resolved
JoshLove-msft
approved these changes
Jan 16, 2025
AzureRestAPISpecReview
removed
the
Versioning-Approved-BugFix
lmazuel
added
BreakingChange-Approved-Benign
markcowl
pushed a commit
to markcowl/azure-rest-api-specs
that referenced
this pull request
Feb 6, 2025
* Added new property SegmentCount to SMSReceived Event * Adding bug fixes * Space Bug fix * Correcting Typo mistake * Changing segmentCount to required parameter * replaced the json files back to the original content * Adding required parameter to AzureComm json file. * removing timestamp as required parameter * code fix * reverting json * trying to fix package.json * fixing the json file * fixes --------- Co-authored-by: jolov <jolov@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Data Plane API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.
Is this review for (select one):
Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!
Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.
Click here for links to tools, specs, guidelines & other good stuff
Tooling
Guidelines & Specifications
Helpful Links
Getting help
write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.