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

[DataFactory]Add support for running staging on multiple sources in parallel #18825

Merged
merged 2 commits into from
May 9, 2022

Conversation

kesharma
Copy link
Contributor

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:

  1. What's the purpose of the update?
    • new service onboarding
    • new API version
    • update existing version for new feature
    • update existing version to fix swagger quality issue in s360
    • Other, please clarify
  2. When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
  3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
  4. If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.
    • SDK of .NET (need service team to ensure code readiness)
    • SDK of Python
    • SDK of Java
    • SDK of Js
    • SDK of Go
    • PowerShell
    • CLI
    • Terraform
    • No refresh required for updates in this PR

Contribution checklist:

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

Applicability: ⚠️

If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

  • Change to data plane APIs
  • Adding new properties
  • All removals

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.

    • Adding a new service
    • Adding new API(s)
    • Adding a new API version
      -[ ] 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.

  • Removing API(s) in a stable version
  • Removing properties in a stable version
  • Removing API version(s) in a stable version
  • Updating API in a stable or public preview version with Breaking Change Validation errors
  • Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

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.

@kesharma kesharma requested a review from shawnxzq as a code owner April 26, 2022 17:18
@openapi-workflow-bot
Copy link

Hi, @kesharma Thanks for your PR. I am workflow bot for review process. Here are some small tips.

  • Please ensure to do self-check against checklists in first PR comment.
  • PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.
  • For specs comparison cross API versions, Use API Specs Comparison Report Generator
  • If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

  • Any feedback about review process or workflow bot, pls contact swagger and tools team. vscswagger@microsoft.com

    @openapi-workflow-bot
    Copy link

    [Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks.

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Apr 26, 2022

    Swagger Validation Report

    ️❌BreakingChange: 23 Errors, 0 Warnings failed [Detail]
    Rule Message
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'ExecutePipelineActivityPolicy' removed or renamed?
    New: stable/2018-06-01/entityTypes/Pipeline.json#L19:3
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L19:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'FailActivity' removed or renamed?
    New: stable/2018-06-01/entityTypes/Pipeline.json#L19:3
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L19:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'FailActivityTypeProperties' removed or renamed?
    New: stable/2018-06-01/entityTypes/Pipeline.json#L19:3
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L19:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'ScriptActivity' removed or renamed?
    New: stable/2018-06-01/entityTypes/Pipeline.json#L19:3
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L19:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'ScriptActivityTypeProperties' removed or renamed?
    New: stable/2018-06-01/entityTypes/Pipeline.json#L19:3
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L19:3
    1021 - AddedAdditionalProperties The new version adds an 'additionalProperties' element.
    New: stable/2018-06-01/entityTypes/Pipeline.json#L5960:9
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L6023:9
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'disableChunking' renamed or removed?
    New: stable/2018-06-01/entityTypes/Pipeline.json#L760:7
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L768:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'disableChunking' renamed or removed?
    New: stable/2018-06-01/entityTypes/Pipeline.json#L803:7
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L815:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'policy' renamed or removed?
    New: stable/2018-06-01/entityTypes/Pipeline.json#L5980:7
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L6040:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'disableCertValidation' renamed or removed?
    New: stable/2018-06-01/entityTypes/Pipeline.json#L6206:7
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L6283:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'parameters' renamed or removed?
    New: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L6673:7
    Old: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L6753:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'rejectedDataLinkedService' renamed or removed?
    New: stable/2018-06-01/entityTypes/DataFlow.json#L217:7
    Old: stable/2018-06-01/entityTypes/DataFlow.json#L332:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'flowlet' renamed or removed?
    New: stable/2018-06-01/entityTypes/DataFlow.json#L217:7
    Old: stable/2018-06-01/entityTypes/DataFlow.json#L332:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'queries' renamed or removed?
    New: stable/2018-06-01/entityTypes/Pipeline.json#L7290:7
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L7438:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'flowlet' renamed or removed?
    New: stable/2018-06-01/entityTypes/DataFlow.json#L202:7
    Old: stable/2018-06-01/entityTypes/DataFlow.json#L317:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'flowlet' renamed or removed?
    New: stable/2018-06-01/entityTypes/DataFlow.json#L157:7
    Old: stable/2018-06-01/entityTypes/DataFlow.json#L260:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'dataset' renamed or removed?
    New: stable/2018-06-01/entityTypes/DataFlow.json#L136:7
    Old: stable/2018-06-01/entityTypes/DataFlow.json#L227:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'linkedService' renamed or removed?
    New: stable/2018-06-01/entityTypes/DataFlow.json#L136:7
    Old: stable/2018-06-01/entityTypes/DataFlow.json#L227:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'flowlet' renamed or removed?
    New: stable/2018-06-01/entityTypes/DataFlow.json#L136:7
    Old: stable/2018-06-01/entityTypes/DataFlow.json#L227:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'rejectedDataLinkedService' renamed or removed?
    New: stable/2018-06-01/entityTypes/DataFlow.json#L179:7
    Old: stable/2018-06-01/entityTypes/DataFlow.json#L286:7
    1033 - RemovedProperty The new version is missing a property found in the old version. Was 'flowlet' renamed or removed?
    New: stable/2018-06-01/entityTypes/DataFlow.json#L179:7
    Old: stable/2018-06-01/entityTypes/DataFlow.json#L286:7
    1045 - AddedOptionalProperty The new version has a new optional property 'sourceStagingConcurrency' that was not found in the old version.
    New: stable/2018-06-01/entityTypes/Pipeline.json#L7234:7
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L7386:7
    1045 - AddedOptionalProperty The new version has a new optional property 'sourceStagingConcurrency' that was not found in the old version.
    New: stable/2018-06-01/entityTypes/Pipeline.json#L7290:7
    Old: stable/2018-06-01/entityTypes/Pipeline.json#L7438:7
    ️⚠️LintDiff: 0 Warnings warning [Detail]
    The following errors/warnings exist before current PR submission:

    Only 30 items are listed, please refer to log for more details.

    Rule Message
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L43
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L43
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L230
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L230
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5225
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5225
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L6037
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L6037
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L6431
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L6431
    R4037 - MissingTypeObject The schema 'ControlActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L189
    R4037 - MissingTypeObject The schema 'ControlActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L189
    R4037 - MissingTypeObject The schema 'ExecutionActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L199
    R4037 - MissingTypeObject The schema 'ExecutionActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L199
    R4037 - MissingTypeObject The schema 'CopyActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L1520
    R4037 - MissingTypeObject The schema 'CopyActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L1520
    R4037 - MissingTypeObject The schema 'CopyActivityTypeProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L1553
    R4037 - MissingTypeObject The schema 'CopyActivityTypeProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L1553
    R4037 - MissingTypeObject The schema 'HDInsightHiveActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5160
    R4037 - MissingTypeObject The schema 'HDInsightHiveActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5160
    R4037 - MissingTypeObject The schema 'HDInsightHiveActivityTypeProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5179
    R4037 - MissingTypeObject The schema 'HDInsightHiveActivityTypeProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5179
    R4037 - MissingTypeObject The schema 'HDInsightPigActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5244
    R4037 - MissingTypeObject The schema 'HDInsightPigActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5244
    R4037 - MissingTypeObject The schema 'HDInsightPigActivityTypeProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5263
    R4037 - MissingTypeObject The schema 'HDInsightPigActivityTypeProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5263
    R4037 - MissingTypeObject The schema 'HDInsightMapReduceActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5299
    R4037 - MissingTypeObject The schema 'HDInsightMapReduceActivity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5299
    R4037 - MissingTypeObject The schema 'HDInsightMapReduceActivityTypeProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5318
    R4037 - MissingTypeObject The schema 'HDInsightMapReduceActivityTypeProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: stable/2018-06-01/entityTypes/Pipeline.json#L5318
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️~[Staging] ApiReadinessCheck succeeded [Detail] [Expand]
    ️️✔️ModelValidation succeeded [Detail] [Expand]
    Validation passes for ModelValidation.
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️️✔️Cross-Version Breaking Changes succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️️✔️PoliCheck succeeded [Detail] [Expand]
    Validation passed for PoliCheck.
    ️️✔️SDK Track2 Validation succeeded [Detail]
    The following errors/warnings exist before current PR submission:
    Rule Message
    "readme":"datafactory/resource-manager/readme.md",
    "tag":"package-2018-06",
    "details":"Error: Plugin prechecker reported failure."
    ️️✔️PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Apr 26, 2022

    Swagger Generation Artifacts

    ️️✔️ApiDocPreview succeeded [Detail] [Expand]

    Only 0 items are rendered, please refer to log for more details.

    ️❌SDK Breaking Change Tracking failed [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️❌ azure-sdk-for-go-track2 failed [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️❌ azure-sdk-for-net failed [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️❌ azure-sdk-for-python-track2 failed [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️⚠️ azure-sdk-for-java warning [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]

    Only 0 items are rendered, please refer to log for more details.

    ️❌ azure-sdk-for-js failed [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️⚠️ azure-resource-manager-schemas warning [Detail]

    Only 0 items are rendered, please refer to log for more details.

    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-workflow-bot
    Copy link

    Hi @kesharma, 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.
    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.
    If you want to know the production traffic statistic, please see ARM Traffic statistic.
    If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback.

    @openapi-workflow-bot
    Copy link

    NewApiVersionRequired reason:

    A service’s API is a contract with customers and is represented by using the api-version query parameter. Changes such as adding an optional property to a request/response or introducing a new operation is a change to the service’s contract and therefore requires a new api-version value. This is critically important for documentation, client libraries, and customer support.

    EXAMPLE: if a customer calls a service in the public cloud using api-version=2020-07-27, the new property or operation may exist but if they call the service in a government cloud, air-gapped cloud, or Azure Stack Hub cloud using the same api-version, the property or operation may not exist. Because there is no clear relationship between the service api-version and the new property/operation, customers can’t trust the documentation and Azure customer have difficulty helping customers diagnose issues. In addition, each client library version documents the service version it supports. When an optional property or new operation is added to a service and its Swagger, new client libraries must be produced to expose this functionality to customers. Without updating the api-version, it is unclear to customers which version of a client library supports these new features.

    @kesharma kesharma changed the title Add support for running staging on multiple sources in parallel [DataFactory]Add support for running staging on multiple sources in parallel May 6, 2022
    @leni-msft
    Copy link
    Contributor

    /azp run

    @azure-pipelines
    Copy link

    Azure Pipelines successfully started running 1 pipeline(s).

    @JeffreyRichter JeffreyRichter added the Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 label May 8, 2022
    @leni-msft leni-msft merged commit c131f16 into Azure:master May 9, 2022
    tjprescott pushed a commit that referenced this pull request Oct 7, 2022
    * Copy solutions files from 2015-06-01-preview
    
    * update API version
    
    * update readme
    
    * Add required to ExternalSecuritySolution
    
    * add new swagger files
    
    * fix errors1
    
    * fix2
    
    * fix 3
    
    * fix 4
    
    * fix4
    
    * fix4
    
    * fix conflict
    
    * fix conflict2
    
    * fix conflict4
    
    * fix conflict 6
    
    * fix conflict 7
    
    * ttt
    
    * rrr
    
    * aaa
    
    * bbb
    
    * fix 10
    
    * Prettier check
    
    * update readme
    
    * fix reference error
    
    * fix comment
    
    * fix conflict
    
    * fic conflict2
    
    * fix conflict3
    
    * fix conflict4
    
    * remove files
    
    * delete externalSecuritySolutions
    
    * add assessments.json
    
    * fix readme.md
    
    * Fix validation errors 1
    
    * Fix validation errors 2
    
    * merge
    
    * Fix validation errors 3
    
    * Fix validation errors 4
    
    * Fix validation errors 5
    
    * Fix validation errors 5
    
    * Fix validation errors 5
    
    * Fix validation errors 6
    
    * Fix validation errors 4
    
    * Fix validation errors 7
    
    * Fix validation errors 8
    
    * Fix validation errors 9
    
    * Fix validation errors 10
    
    * fix validation errors 11
    
    * fix validation errors 11
    
    * ix validation errors 12
    
    * ix validation errors 13
    
    * fix validation errors 14
    
    * Fix validation errors 15
    
    * Fix validation errors 16
    
    * run prettier
    
    * adding Services APIs
    
    * more changes
    
    * updated examples
    
    * Defining the APIs for the new NSP resource
    
    * IoT Central Public API 1.1-preview Oct Release (#16514)
    
    * Add new 2.0-preview.1 version for IoT Central
    
    * fix typo on enum value
    
    * rollback 1.0 changes, applied 2.0-preview.1
    
    * fix typo
    
    * remove non-used examples
    
    * fix style
    
    * update version from 2.0-preview.1 to 1.1-preview
    
    * update code review comments, fix patch consumes with json-patch support, fix examples for fileupload
    
    * add nextLink to collection of orgs
    
    * fix typo
    
    * fix wrong position of paging
    
    * fix the paging
    
    * add . to description
    
    * update default to use enum for api-version
    
    * add oct release with query, cde v2, device filter, device template filter, relationship, edge template, simplified template patching
    
    * update examples
    
    * fix lint error, model validation
    
    * fix missing type in examples, remove url format
    
    * fix ID case
    
    * fix id case
    
    * fix ID case
    
    * add iotc query language reference
    
    * fix typo
    
    * test
    
    * SecuritySolution test
    
    * 2
    
    * org
    
    * 1
    
    * [DataFactory]Add support for running staging on multiple sources in parallel (#18825)
    
    * Add support for running staging on multiple sources in parallel
    
    * update
    
    * Add default accountid (#19417)
    
    Similar PR was merged into Main.
    s360 ticket still leading to this branch - so we are pushing the pull request with the same fixes here.
    
    * Adds base for updating Creator from version preview/2.0 to version 2022-09-01-preview
    
    * Updates readme
    
    * Updates API version in new specs and examples
    
    * Removed api docs except dataset
    
    * Dataset 2022-09-01-preview changes
    
    * Readme changes
    
    * Merge Commit
    
    * Minor changes
    
    * Change in readme.md
    
    * Merging from main
    
    * Merging from main
    
    * Udids in List Response
    
    * small changes
    
    * small change
    
    * Wrong update
    
    * outputOntology
    
    * outputOntology
    
    * Append Example
    
    Co-authored-by: Arik Riklin <arik.riklin@microsoft.com>
    Co-authored-by: ariklin <ariklin@microsoft.com>
    Co-authored-by: Hari Prasad Perabattula <harics24@users.noreply.github.com>
    Co-authored-by: Meha Kaushik <kaushik.meha@gmail.com>
    Co-authored-by: Meha Kaushik <mekaushi@microsoft.com>
    Co-authored-by: Amit Singh <31076927+amisi01@users.noreply.github.com>
    Co-authored-by: Hari Prasad Perabattula <haperaba@microsoft.com>
    Co-authored-by: REDMOND\amisi <amisi@microsoft.com>
    Co-authored-by: Johnson Yang <hayang@microsoft.com>
    Co-authored-by: kesharma <74746991+kesharma@users.noreply.github.com>
    Co-authored-by: Tal Shoham <87926500+tshoham@users.noreply.github.com>
    Co-authored-by: tejitpabari <tejitpabari@microsoft.com>
    anandanthony pushed a commit to anandMicro/azure-rest-api-specs that referenced this pull request Dec 16, 2022
    * Copy solutions files from 2015-06-01-preview
    
    * update API version
    
    * update readme
    
    * Add required to ExternalSecuritySolution
    
    * add new swagger files
    
    * fix errors1
    
    * fix2
    
    * fix 3
    
    * fix 4
    
    * fix4
    
    * fix4
    
    * fix conflict
    
    * fix conflict2
    
    * fix conflict4
    
    * fix conflict 6
    
    * fix conflict 7
    
    * ttt
    
    * rrr
    
    * aaa
    
    * bbb
    
    * fix 10
    
    * Prettier check
    
    * update readme
    
    * fix reference error
    
    * fix comment
    
    * fix conflict
    
    * fic conflict2
    
    * fix conflict3
    
    * fix conflict4
    
    * remove files
    
    * delete externalSecuritySolutions
    
    * add assessments.json
    
    * fix readme.md
    
    * Fix validation errors 1
    
    * Fix validation errors 2
    
    * merge
    
    * Fix validation errors 3
    
    * Fix validation errors 4
    
    * Fix validation errors 5
    
    * Fix validation errors 5
    
    * Fix validation errors 5
    
    * Fix validation errors 6
    
    * Fix validation errors 4
    
    * Fix validation errors 7
    
    * Fix validation errors 8
    
    * Fix validation errors 9
    
    * Fix validation errors 10
    
    * fix validation errors 11
    
    * fix validation errors 11
    
    * ix validation errors 12
    
    * ix validation errors 13
    
    * fix validation errors 14
    
    * Fix validation errors 15
    
    * Fix validation errors 16
    
    * run prettier
    
    * adding Services APIs
    
    * more changes
    
    * updated examples
    
    * Defining the APIs for the new NSP resource
    
    * IoT Central Public API 1.1-preview Oct Release (Azure#16514)
    
    * Add new 2.0-preview.1 version for IoT Central
    
    * fix typo on enum value
    
    * rollback 1.0 changes, applied 2.0-preview.1
    
    * fix typo
    
    * remove non-used examples
    
    * fix style
    
    * update version from 2.0-preview.1 to 1.1-preview
    
    * update code review comments, fix patch consumes with json-patch support, fix examples for fileupload
    
    * add nextLink to collection of orgs
    
    * fix typo
    
    * fix wrong position of paging
    
    * fix the paging
    
    * add . to description
    
    * update default to use enum for api-version
    
    * add oct release with query, cde v2, device filter, device template filter, relationship, edge template, simplified template patching
    
    * update examples
    
    * fix lint error, model validation
    
    * fix missing type in examples, remove url format
    
    * fix ID case
    
    * fix id case
    
    * fix ID case
    
    * add iotc query language reference
    
    * fix typo
    
    * test
    
    * SecuritySolution test
    
    * 2
    
    * org
    
    * 1
    
    * [DataFactory]Add support for running staging on multiple sources in parallel (Azure#18825)
    
    * Add support for running staging on multiple sources in parallel
    
    * update
    
    * Add default accountid (Azure#19417)
    
    Similar PR was merged into Main.
    s360 ticket still leading to this branch - so we are pushing the pull request with the same fixes here.
    
    * Adds base for updating Creator from version preview/2.0 to version 2022-09-01-preview
    
    * Updates readme
    
    * Updates API version in new specs and examples
    
    * Removed api docs except dataset
    
    * Dataset 2022-09-01-preview changes
    
    * Readme changes
    
    * Merge Commit
    
    * Minor changes
    
    * Change in readme.md
    
    * Merging from main
    
    * Merging from main
    
    * Udids in List Response
    
    * small changes
    
    * small change
    
    * Wrong update
    
    * outputOntology
    
    * outputOntology
    
    * Append Example
    
    Co-authored-by: Arik Riklin <arik.riklin@microsoft.com>
    Co-authored-by: ariklin <ariklin@microsoft.com>
    Co-authored-by: Hari Prasad Perabattula <harics24@users.noreply.github.com>
    Co-authored-by: Meha Kaushik <kaushik.meha@gmail.com>
    Co-authored-by: Meha Kaushik <mekaushi@microsoft.com>
    Co-authored-by: Amit Singh <31076927+amisi01@users.noreply.github.com>
    Co-authored-by: Hari Prasad Perabattula <haperaba@microsoft.com>
    Co-authored-by: REDMOND\amisi <amisi@microsoft.com>
    Co-authored-by: Johnson Yang <hayang@microsoft.com>
    Co-authored-by: kesharma <74746991+kesharma@users.noreply.github.com>
    Co-authored-by: Tal Shoham <87926500+tshoham@users.noreply.github.com>
    Co-authored-by: tejitpabari <tejitpabari@microsoft.com>
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    6 participants