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

[Hub Generated] Review request for Microsoft.Network to add version stable/2021-06-09 #14745

Draft
wants to merge 16 commits into
base: main
Choose a base branch
from

Conversation

bhmohant
Copy link

@bhmohant bhmohant commented Jun 9, 2021

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.

Changelog

Please ensure to add changelog with 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 you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
  3. When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
  4. If it's an update to existing version, please select SDKs of specific language and CLIs that require refresh after 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, no need to refresh 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

  • Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

    • Adding new API(s)
    • Adding a new API version
    • Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
    • Adding a new service
  • Please 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 there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

  • Removing API(s) in stable version
  • Removing properties in stable version
  • Removing API version(s) in stable version
  • Updating API in 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.

Task: https://msazure.visualstudio.com/One/_workitems/edit/10072622

@openapi-workflow-bot
Copy link

Hi, @bhmohant 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. vsswagger@microsoft.com

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Jun 9, 2021

    Swagger Validation Report

    ️❌BreakingChange: 1 Errors, 0 Warnings failed [Detail]
    Rule Message
    Runtime Exception "new":"https://github.com/Azure/azure-rest-api-specs/blob/12fc49e2c8db2d737c163a186446a2f24643a1f0/specification/frontdoor/resource-manager/Microsoft.Network/stable/2020-11-01/webapplicationfirewall.json",
    "old":"https://github.com/Azure/azure-rest-api-specs/blob/master/specification/frontdoor/resource-manager/Microsoft.Network/stable/2020-11-01/webapplicationfirewall.json",
    "details":"Command failed: dotnet /home/vsts/work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/@azure/oad@0.8.11/node_modules/@azure/oad/dlls/OpenApiDiff.dll -o /tmp/old-resolved.json -n /tmp/new-resolved.json
    Unhandled Exception: Newtonsoft.Json.JsonSerializationException: Error converting value False to type 'AutoRest.Swagger.Model.Schema'. Path 'definitions.ManagedRuleSetDefinitionProperties.properties.supportedSkus.additionalProperties',
    line 1,
    position 31589. ---> System.ArgumentException: Could not cast or convert from System.Boolean to AutoRest.Swagger.Model.Schema.\n at Newtonsoft.Json.Utilities.ConvertUtils.EnsureTypeAssignable(Object value,
    Type initialType,
    Type targetType)\n at Newtonsoft.Json.Utilities.ConvertUtils.ConvertOrCast(Object initialValue,
    CultureInfo culture,
    Type targetType)\n at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EnsureType(JsonReader reader,
    Object value,
    CultureInfo culture,
    JsonContract contract,
    Type targetType)\n --- End of inner exception stack"
    ️❌LintDiff: 4 Errors, 0 Warnings failed [Detail]
    The following errors/warnings are introduced by current PR:
    Rule Message
    AutoRest exception "readme":"frontdoor/resource-manager/readme.md",
    "tag":"package-2020-11",
    "details":"Newtonsoft.Json.JsonSerializationException: Error converting value False to type 'OpenAPI.Validator.Model.Schema'. Path 'properties.supportedSkus.additionalProperties',
    line 61,
    position 35. ---> System.ArgumentException: Could not cast or convert from System.Boolean to OpenAPI.Validator.Model.Schema. at Newtonsoft.Json.Utilities.ConvertUtils.EnsureTypeAssignable(Object value,
    Type initialType,
    Type targetType) at Newtonsoft.Json.Utilities.ConvertUtils.ConvertOrCast(Object initialValue,
    CultureInfo culture,
    Type targetType) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EnsureType(JsonReader reader,
    Object value,
    CultureInfo culture,
    JsonContract contract,
    Type targetType) --- End of inner exception stack trace --- at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EnsureType(JsonReader reader,
    Object value,
    CultureInfo culture,
    JsonContract contract,
    Type targetType) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue(JsonProperty property,
    Jso"
    AutoRest exception "readme":"frontdoor/resource-manager/readme.md",
    "tag":"package-2020-11",
    "details":"swagger-document/classic-openapi-validator - FAILED"
    AutoRest exception "readme":"frontdoor/resource-manager/readme.md",
    "tag":"package-2020-11",
    "details":"Error: Plugin classic-openapi-validator reported failure."
    AutoRest exception "readme":"frontdoor/resource-manager/readme.md",
    "tag":"package-2020-11",
    "details":"swagger-document/individual/classic-openapi-validator - FAILED"


    The following errors/warnings exist before current PR submission:

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

    Rule Message
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/providers/Microsoft.Network/NetworkExperimentProfiles'
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L55
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles'
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L97
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}'
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L142
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/PreconfiguredEndpoints'
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L356
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/Experiments'
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L404
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/Experiments/{experimentName}'
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L452
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/Experiments/{experimentName}/LatencyScorecard'
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L678
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/Experiments/{experimentName}/Timeseries'
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L756
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/FrontDoorWebApplicationFirewallPolicies/{policyName}'
    Location: Microsoft.Network/stable/2020-11-01/webapplicationfirewall.json#L79
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/providers/Microsoft.Network/FrontDoorWebApplicationFirewallManagedRuleSets'
    Location: Microsoft.Network/stable/2020-11-01/webapplicationfirewall.json#L221
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L80
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L125
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L173
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L237
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L297
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L341
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L387
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L435
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L486
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L550
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L613
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L663
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L742
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2019-11-01/networkexperiment.json#L851
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2020-05-01/frontdoor.json#L70
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2020-05-01/frontdoor.json#L115
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2020-05-01/frontdoor.json#L146
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2020-05-01/frontdoor.json#L188
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2020-05-01/frontdoor.json#L233
    R4007 - DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
    Location: Microsoft.Network/stable/2020-05-01/frontdoor.json#L294
    ️⚠️Avocado: 1 Warnings warning [Detail]
    Rule Message
    ⚠️ MULTIPLE_API_VERSION The default tag contains multiple API versions swaggers.
    readme: specification/frontdoor/resource-manager/readme.md
    tag: specification/frontdoor/resource-manager/readme.md#tag-package-2020-11
    ️️✔️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.
    ️⚠️[Staging] SDK Track2 Validation: 0 Warnings warning [Detail]
    The following errors/warnings are introduced by current PR:
    The following errors/warnings exist before current PR submission:
    Rule Message
    ⚠️ PreCheck/PropertyRedeclarationWarning "readme":"frontdoor/resource-manager/readme.md",
    "tag":"package-2020-11",
    "details":"Schema 'Profile' has a property 'name' that is already declared the parent schema 'Resource' but 'readonly' has been changed -- this is not permitted. The property has been removed from Profile"
    ⚠️ PreCheck/PropertyRedeclarationWarning "readme":"frontdoor/resource-manager/readme.md",
    "tag":"package-2020-11",
    "details":"Schema 'Experiment' has a property 'name' that is already declared the parent schema 'Resource' but isn't significantly different. The property has been removed from Experiment"
    ⚠️ PreCheck/PropertyRedeclarationWarning "readme":"frontdoor/resource-manager/readme.md",
    "tag":"package-2020-11",
    "details":"Schema 'PreconfiguredEndpoint' has a property 'name' that is already declared the parent schema 'Resource' but 'readonly' has been changed -- this is not permitted. The property has been removed from PreconfiguredEndpoint"
    💬 AutorestCore/Exception "readme":"frontdoor/resource-manager/readme.md",
    "tag":"package-2020-11",
    "details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)"
    ️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    Posted by Swagger Pipeline | How to fix these errors?

    @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 Jun 9, 2021

    Swagger Generation Artifacts

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

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

    ️️✔️[Staging] SDK Breaking Change Tracking succeeded [Detail] [Expand]

    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 failed [Detail]

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

    ️⚠️ azure-sdk-for-python-track2 warning [Detail]

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

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

    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 succeeded [Detail] [Expand]

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

    Posted by Swagger Pipeline | How to fix these errors?

    @bhmohant
    Copy link
    Author

    bhmohant commented Jun 9, 2021

    /azp run unifiedPipeline

    @azure-pipelines
    Copy link

    No pipelines are associated with this pull request.

    @bhmohant bhmohant requested a review from eschwabe June 10, 2021 17:32
    @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.

    @bhmohant
    Copy link
    Author

    /azp run unifiedPipeline

    @azure-pipelines
    Copy link

    No pipelines are associated with this pull request.

    @bhmohant bhmohant self-assigned this Jun 10, 2021
    @bhmohant
    Copy link
    Author

    /azp run unifiedPipeline

    @azure-pipelines
    Copy link

    No pipelines are associated with this pull request.

    Copy link

    Next Steps to Merge

    ⌛ Please wait. Next steps to merge this PR are being evaluated by automation. ⌛

    Copy link
    Contributor

    @bhmohant please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

    @microsoft-github-policy-service agree [company="{your company}"]
    

    Options:

    • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
    @microsoft-github-policy-service agree
    
    • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
    @microsoft-github-policy-service agree company="Microsoft"
    
    Contributor License Agreement

    Contribution License Agreement

    This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
    and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
    contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
    date below.

    1. Definitions.
      “Code” means the computer software code, whether in human-readable or machine-executable form,
      that is delivered by You to Microsoft under this Agreement.
      “Project” means any of the projects owned or managed by Microsoft and offered under a license
      approved by the Open Source Initiative (www.opensource.org).
      “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
      Project, including but not limited to communication on electronic mailing lists, source code control
      systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
      discussing and improving that Project, but excluding communication that is conspicuously marked or
      otherwise designated in writing by You as “Not a Submission.”
      “Submission” means the Code and any other copyrightable material Submitted by You, including any
      associated comments and documentation.
    2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
      Project. This Agreement covers any and all Submissions that You, now or in the future (except as
      described in Section 4 below), Submit to any Project.
    3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
      Should You wish to Submit materials that are not Your original work, You may Submit them separately
      to the Project if You (a) retain all copyright and license information that was in the materials as You
      received them, (b) in the description accompanying Your Submission, include the phrase “Submission
      containing materials of a third party:” followed by the names of the third party and any licenses or other
      restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
      guidelines concerning Submissions.
    4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
      for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
      Submission is made in the course of Your work for an employer or Your employer has intellectual
      property rights in Your Submission by contract or applicable law, You must secure permission from Your
      employer to make the Submission before signing this Agreement. In that case, the term “You” in this
      Agreement will refer to You and the employer collectively. If You change employers in the future and
      desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
      and secure permission from the new employer before Submitting those Submissions.
    5. Licenses.
    • Copyright License. You grant Microsoft, and those who receive the Submission directly or
      indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
      Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
      the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
      parties.
    • Patent License. You grant Microsoft, and those who receive the Submission directly or
      indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
      Your patent claims that are necessarily infringed by the Submission or the combination of the
      Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
      import or otherwise dispose of the Submission alone or with the Project.
    • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
      No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
      granted by implication, exhaustion, estoppel or otherwise.
    1. Representations and Warranties. You represent that You are legally entitled to grant the above
      licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
      have disclosed under Section 3). You represent that You have secured permission from Your employer to
      make the Submission in cases where Your Submission is made in the course of Your work for Your
      employer or Your employer has intellectual property rights in Your Submission by contract or applicable
      law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
      have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
      You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
      REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
      EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
      PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
      NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
    2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
      You later become aware that would make Your representations in this Agreement inaccurate in any
      respect.
    3. Information about Submissions. You agree that contributions to Projects and information about
      contributions may be maintained indefinitely and disclosed publicly, including Your name and other
      information that You submit with Your Submission.
    4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
      the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
      Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
      exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
      defenses of lack of personal jurisdiction and forum non-conveniens.
    5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
      supersedes any and all prior agreements, understandings or communications, written or oral, between
      the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    5 participants