[@azure/eventgrid] Adding new events for EG Version 5.3.0 #28891
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
sarangan12
requested review from
bterlson,
xirzec,
jeremymeng and
mpodwysocki
as code owners
|
/azp run js - eventgrid - ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
maorleger
approved these changes
Mar 13, 2024
3 tasks
sarangan12
added a commit
that referenced
this pull request
Apr 10, 2024
### Packages impacted by this PR @azure/eventgrid ### Issues associated with this PR NA ### Describe the problem that is addressed by this PR The EventGrid Service Team has added 3 new events. The SDK must be regenerated to include the code changes related to these 3 new events. The SDK minor version has been updated. - `Microsoft.Communication.AdvancedMessageDeliveryStatusUpdated` - `Microsoft.Communication.AdvancedMessageReceived` - `Microsoft.Communication.RouterWorkerUpdated` ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? There are no specific/complex design scenarios for this task. It is a straightforward regenerate and some standard changes to the custom layer of the code. ### Are there test cases added in this PR? _(If not, why?)_ No. This item is standard and we need not add test cases for every new events. The existing cases would be sufficient. ### Provide a list of related PRs _(if any)_ - #27384 (This is the PR that adds similar events to the SDK in the 4.15.0 release) - #26939 (This is the PR that adds similar events to the SDK in the 4.14.0 release) - #26020 (This is the PR that adds similar events to the SDK in the 4.13.0 release) - #28176 (This is the PR that adds similar events to the SDK in the 5.1.0 release) - #28513 (This is the PR that adds similar events to the SDK in the 5.2.0 release) - #28891 (This is the PR that adds similar events to the SDK in the 5.3.0 release) ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ `autorest --typescript swagger\README.md` ### Checklists - [X] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [X] Added a changelog (if necessary)
3 tasks
3 tasks
sarangan12
added a commit
that referenced
this pull request
Aug 20, 2024
### Packages impacted by this PR @azure/eventgrid ### Issues associated with this PR NA ### Describe the problem that is addressed by this PR This PR consists of the following changes: - A new field `accessTier` is added to the `StorageBlobCreatedEventData` object. - Two new fields `accessTier` & `previousTier` are added to the StorageBlobTierChangedEventData object. - The properties `api`, `blobType`, `clientRequestId`, `contentLength`, `contentOffset`, `contentType`, `eTag`, `identity`, `requestId`, `sequencer`, `storageDiagnostics` & `url` in `StorageBlobCreatedEventData` have been made optional. - The properties `api`, `blobType`, `clientRequestId`, `contentLength`, `contentType`,`identity`, `requestId`, `sequencer`, `storageDiagnostics` & `url` in `StorageBlobTierChangedEventData` have been made optional. ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? There are no specific/complex design scenarios for this task. It is a straightforward regenerate and some standard changes to the custom layer of the code. ### Are there test cases added in this PR? _(If not, why?)_ No. This item is standard and we need not add test cases for every new events. The existing cases would be sufficient. ### Provide a list of related PRs _(if any)_ - #28176 (This is the PR that adds similar events to the SDK in the 5.1.0 release) - #28513 (This is the PR that adds similar events to the SDK in the 5.2.0 release) - #28891 (This is the PR that adds similar events to the SDK in the 5.3.0 release) - #29035 (This is the PR that adds similar events to the SDK in the 5.4.0 release) - #29872 (This is the PR that adds similar events to the SDK in the 5.5.0 release) ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ```autorest --typescript swagger\README.md``` ### Checklists - [X] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [X] Added a changelog (if necessary) --------- Co-authored-by: Jeremy Meng <yumeng@microsoft.com>
3 tasks
sarangan12
added a commit
that referenced
this pull request
Sep 23, 2024
### Packages impacted by this PR @azure/eventgrid ### Issues associated with this PR NA ### Describe the problem that is addressed by this PR This PR consists of the following changes: - A new property `tierToColdSummary` is added to the `StorageLifecyclePolicyCompletedEventData` interface. ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? There are no specific/complex design scenarios for this task. It is a straightforward regenerate and some standard changes to the custom layer of the code. ### Are there test cases added in this PR? _(If not, why?)_ No. This item is standard and we need not add test cases for every new events. The existing cases would be sufficient. ### Provide a list of related PRs _(if any)_ - #28176 (This is the PR that adds similar events to the SDK in the 5.1.0 release) - #28513 (This is the PR that adds similar events to the SDK in the 5.2.0 release) - #28891 (This is the PR that adds similar events to the SDK in the 5.3.0 release) - #29035 (This is the PR that adds similar events to the SDK in the 5.4.0 release) - #29872 (This is the PR that adds similar events to the SDK in the 5.5.0 release) - #30811 (This is the PR that adds similar events to the SDK in the 5.6.0 release) ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ```autorest --typescript swagger\README.md``` ### Checklists - [X] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [X] Added a changelog (if necessary)
3 tasks
sarangan12
added a commit
that referenced
this pull request
Oct 11, 2024
### Packages impacted by this PR @azure/eventgrid ### Issues associated with this PR NA ### Describe the problem that is addressed by this PR This PR consists of the following changes: - A new property `onBehalfOfCallee` is added to the `AcsIncomingCallEventData` interface. - The property `serializedName` has been removed from `MediaJobOutputProgressEventData` & `MediaJobScheduledEventData` models. ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? There are no specific/complex design scenarios for this task. It is a straightforward regenerate and some standard changes to the custom layer of the code. ### Are there test cases added in this PR? _(If not, why?)_ No. This item is standard and we need not add test cases for every new events. The existing cases would be sufficient. ### Provide a list of related PRs _(if any)_ - #28513 (This is the PR that adds similar events to the SDK in the 5.2.0 release) - #28891 (This is the PR that adds similar events to the SDK in the 5.3.0 release) - #29035 (This is the PR that adds similar events to the SDK in the 5.4.0 release) - #29872 (This is the PR that adds similar events to the SDK in the 5.5.0 release) - #30811 (This is the PR that adds similar events to the SDK in the 5.6.0 release) - #31186 (This is the PR that adds similar events to the SDK in the 5.7.0 release) ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ```autorest --typescript swagger\README.md``` ### Checklists - [X] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [X] Added a changelog (if necessary)
3 tasks
3 tasks
sarangan12
added a commit
that referenced
this pull request
Dec 2, 2024
### Packages impacted by this PR @Azure/eventgrid ### Issues associated with this PR NA ### Describe the problem that is addressed by this PR This PR consists of the following changes: - Added new System Events: - `Microsoft.ResourceNotifications.ContainerServiceEventResources.ScheduledEventEmitted` - A new property `policyRunSummary` has been added to `StorageLifecyclePolicyCompletedEventData` interface. - New properties `StorageLifecycleCompletionStatus` and `KnownStorageLifecycleCompletionStatus` have been added. ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? There are no specific/complex design scenarios for this task. It is a straightforward regenerate and some standard changes to the custom layer of the code. ### Are there test cases added in this PR? _(If not, why?)_ No. This item is standard and we need not add test cases for every new events. The existing cases would be sufficient. ### Provide a list of related PRs _(if any)_ - #28176 (This is the PR that adds similar events to the SDK in the 5.1.0 release) - #28513 (This is the PR that adds similar events to the SDK in the 5.2.0 release) - #28891 (This is the PR that adds similar events to the SDK in the 5.3.0 release) - #29035 (This is the PR that adds similar events to the SDK in the 5.4.0 release) - #29872 (This is the PR that adds similar events to the SDK in the 5.5.0 release) - #30811 (This is the PR that adds similar events to the SDK in the 5.6.0 release) ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ```autorest --typescript swagger\README.md``` ### Checklists - [X] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [X] Added a changelog (if necessary)
This was referenced Jan 6, 2025
sarangan12
added a commit
that referenced
this pull request
Jan 21, 2025
### Packages impacted by this PR `@azure/eventgrid` ### Issues associated with this PR Azure/azure-rest-api-specs#32004 ### Describe the problem that is addressed by this PR This PR consists of the following changes: - Added `internetMessageId` property to `AcsEmailDeliveryReportReceivedEventData`. - Added `recipientMailServerHostName` property to `AcsEmailDeliveryReportStatusDetails`. - For `AcsSmsReceivedEventData`: - Added `segmentCount` property - Made `message` & `receivedTimestamp` properties optional. ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? There are no specific/complex design scenarios for this task. It is a straightforward regenerate and some standard changes to the custom layer of the code. ### Are there test cases added in this PR? _(If not, why?)_ No. This item is standard and we need not add test cases for every new events. The existing cases would be sufficient. ### Provide a list of related PRs _(if any)_ - #28176 (This is the PR that adds similar events to the SDK in the 5.1.0 release) - #28513 (This is the PR that adds similar events to the SDK in the 5.2.0 release) - #28891 (This is the PR that adds similar events to the SDK in the 5.3.0 release) - #29035 (This is the PR that adds similar events to the SDK in the 5.4.0 release) - #29872 (This is the PR that adds similar events to the SDK in the 5.5.0 release) - #30811 (This is the PR that adds similar events to the SDK in the 5.6.0 release) - #32011 (This is the PR that adds similar events to the SDK in the 5.9.0 release) ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ```autorest --typescript swagger\README.md``` ### Checklists - [X] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [X] Added a changelog (if necessary)
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.
Packages impacted by this PR
@azure/eventgrid
Issues associated with this PR
NA
Describe the problem that is addressed by this PR
The EventGrid Service Team has added 2 new events. The SDK must be regenerated to include the code changes related to these 2 new events. The SDK minor version has been updated.
Microsoft.ApiCenter.ApiDefinitionAddedMicrosoft.ApiCenter.ApiDefinitionUpdatedWhat are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
There are no specific/complex design scenarios for this task. It is a straightforward regenerate and some standard changes to the custom layer of the code.
Are there test cases added in this PR? (If not, why?)
No. This item is standard and we need not add test cases for every new events. The existing cases would be sufficient.
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
autorest --typescript swagger\README.mdChecklists