[Stream Analytics] Fix s360 for 2021 preview version #18305
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
… into roslu/2021preview
…into roslu/2021preview
|
/azp run |
|
Swagger pipeline started successfully, please wait for status update in this comment. |
1 similar comment
|
Swagger pipeline started successfully, please wait for status update in this comment. |
|
Swagger pipeline started successfully, please wait for status update in this comment. |
1 similar comment
|
Swagger pipeline started successfully, please wait for status update in this comment. |
Swagger Generation Artifacts
|
|
Azure Pipelines successfully started running 1 pipeline(s). |
This was referenced Mar 17, 2022
JeffreyRichter
added
the
Approved-BreakingChange
|
@jianyexi please help check the lint exception |
|
NewApiVersionRequired reason: |
jianyexi
reviewed
Mar 25, 2022
...ics/resource-manager/Microsoft.StreamAnalytics/preview/2021-10-01-preview/streamingjobs.json
Show resolved
Hide resolved
|
Hi @roslynlu, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
jianyexi
approved these changes
Mar 25, 2022
This was referenced Mar 25, 2022
ghost
pushed a commit
to Azure/azure-resource-manager-schemas
that referenced
this pull request
Mar 25, 2022
visingl
pushed a commit
that referenced
this pull request
Mar 30, 2022
* Add blockchain to latest profile * Add additional types * add azure function * add authenticationMode to blob input, AzFunction and DW ex files * update api version in 2021 preview ex files * fix api version * fix password * try to run model validation again * update pe to readonly * 2021 preview features * fix validation errors * more fixes * add aggregate func, which should be GA * rename new refreshType object Co-authored-by: Mark Cowlishaw <markcowl@microsoft.com> Co-authored-by: Roslyn Lu <roslu@microsoft.com>
yanlingms
added a commit
to yanlingms/azure-rest-api-specs
that referenced
this pull request
Apr 12, 2022
FredericHeem
pushed a commit
to grucloud/azure-rest-api-specs
that referenced
this pull request
May 16, 2022
* Add blockchain to latest profile * Add additional types * add azure function * add authenticationMode to blob input, AzFunction and DW ex files * update api version in 2021 preview ex files * fix api version * fix password * try to run model validation again * update pe to readonly * 2021 preview features * fix validation errors * more fixes * add aggregate func, which should be GA * rename new refreshType object Co-authored-by: Mark Cowlishaw <markcowl@microsoft.com> Co-authored-by: Roslyn Lu <roslu@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.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.