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

Update batch dataplane for version 2021-01-01-13.0 - Data Plane #12426

Closed
wants to merge 4 commits into from

Conversation

paterasMSFT
Copy link
Contributor

@paterasMSFT paterasMSFT commented Jan 13, 2021

New features in this release are:

  • Managed identity support for pools
  • Virtual machine extension support for nodes
  • Availability zone support for pools

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. Service has already begun to roll out.
  3. When you expect to publish swagger? Please provide date, or month to public if date is not available yet. ASAP (delivery due 01-01-2021)
  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
    • 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 API 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 version with Breaking Change Validation errors
  • Updating API(s) in preview over 1 year

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.

@openapi-workflow-bot
Copy link

Hi, @paterasMSFT 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 Jan 13, 2021

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️LintDiff succeeded [Detail] [Expand]
    Validation passes for LintDiff.

    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ModelValidation succeeded [Detail] [Expand]
    Validation passes for ModelValidation.
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️️✔️[Staging] Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
    There are no breaking changes.

    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️⚠️[Staging] SDK Track2 Validation: 154 Warnings warning [Detail] Only 10 items are listed, please refer to log for more details.

    Rule Message
    ⚠️ PreCheck/SchemaMissingType "readme":"batch/data-plane/readme.md",
    "tag":"package-2021-01.13.0",
    "details":"The schema 'PoolUsageMetrics' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'"
    ⚠️ PreCheck/SchemaMissingType "readme":"batch/data-plane/readme.md",
    "tag":"package-2021-01.13.0",
    "details":"The schema 'PoolListUsageMetricsResult' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'"
    ⚠️ PreCheck/SchemaMissingType "readme":"batch/data-plane/readme.md",
    "tag":"package-2021-01.13.0",
    "details":"The schema 'ImageInformation' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'"
    ⚠️ PreCheck/SchemaMissingType "readme":"batch/data-plane/readme.md",
    "tag":"package-2021-01.13.0",
    "details":"The schema 'AuthenticationTokenSettings' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'"
    ⚠️ PreCheck/SchemaMissingType "readme":"batch/data-plane/readme.md",
    "tag":"package-2021-01.13.0",
    "details":"The schema 'AccountListSupportedImagesResult' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'"
    ⚠️ PreCheck/SchemaMissingType "readme":"batch/data-plane/readme.md",
    "tag":"package-2021-01.13.0",
    "details":"The schema 'UsageStatistics' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'"
    ⚠️ PreCheck/SchemaMissingType "readme":"batch/data-plane/readme.md",
    "tag":"package-2021-01.13.0",
    "details":"The schema 'ResourceStatistics' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'"
    ⚠️ PreCheck/SchemaMissingType "readme":"batch/data-plane/readme.md",
    "tag":"package-2021-01.13.0",
    "details":"The schema 'PoolStatistics' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'"
    ⚠️ PreCheck/SchemaMissingType "readme":"batch/data-plane/readme.md",
    "tag":"package-2021-01.13.0",
    "details":"The schema 'JobStatistics' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'"
    ⚠️ PreCheck/SchemaMissingType "readme":"batch/data-plane/readme.md",
    "tag":"package-2021-01.13.0",
    "details":"The schema 'NameValuePair' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'"
    ️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Jan 13, 2021

    Swagger Generation Artifacts

    ️️✔️[Staging] ApiDocPreview succeeded [Detail] [Expand]
     Please click here to preview with your @microsoft account. 
    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
    ️❌ azure-sdk-for-js failed [Detail]
    • Failed [Logs] Generate from 4e733eb36d56479d2ce7fa31f3943623cf2214f6. SDK Automation 14.0.0
      warn	Skip initScript due to not configured
      command	autorest --version=V2 --typescript --license-header=MICROSOFT_MIT_NO_VERSION --use=@microsoft.azure/autorest.typescript@4.4.4 --typescript-sdks-folder=/home/vsts/work/1/s/azure-sdk-for-js/azure-sdk-for-js ../../azure-rest-api-specs/specification/batch/data-plane/readme.md
      cmdout	[Autorest] WARNING: HEAD 'getPropertiesFromTask' method missing 404 status code section -- this might be unintentional.
      cmdout	[Autorest] WARNING: HEAD 'getPropertiesFromComputeNode' method missing 404 status code section -- this might be unintentional.
    • @azure/batch [View full logs]  [Preview SDK Changes]
      error	Script return with result [failed] code [2] signal [null] cwd [azure-sdk-for-js/azure-sdk-for-js/sdk/batch/batch]: npm pack --silent
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-workflow-bot openapi-workflow-bot bot added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jan 13, 2021
    @openapi-workflow-bot
    Copy link

    Hi, @paterasMSFT your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @tjprescott

    @dpwatrous dpwatrous added NotReadyForReview <valid label in PR review process>It is in draft for swagger or not swagger PR and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jan 14, 2021
    @dpwatrous
    Copy link
    Member

    This PR was split off from #12393 (which contained both data and management planes previously). Added @anuchandy as the reviewer since he has already reviewed these changes in the other PR.

    We're in a bit of a holding pattern here while we sort through an issue on the service side with VM extensions, so marked this as not ready for review. Will update when we have things sorted on our end.

    @paterasMSFT paterasMSFT force-pushed the Batch-update-data-plane-2021-01-01.13.0 branch from 44a2c13 to 32ec4dd Compare January 14, 2021 17:17
    @paterasMSFT paterasMSFT force-pushed the Batch-update-data-plane-2021-01-01.13.0 branch from 32ec4dd to 487da4b Compare January 14, 2021 19:21
    @akning-ms
    Copy link
    Contributor

    /azp run

    @azure-pipelines
    Copy link

    Azure Pipelines successfully started running 2 pipeline(s).

    @dpwatrous dpwatrous added the DoNotMerge <valid label in PR review process> use to hold merge after approval label Jan 21, 2021
    @dpwatrous
    Copy link
    Member

    Marked as DoNotMerge until the issue with virtual machine extensions is resolved on the service side. (Even though this likely won't affect the data plane swagger)

    @ghost
    Copy link

    ghost commented Feb 21, 2021

    Hi, @paterasMSFT. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

    @ghost ghost added the no-recent-activity label Feb 21, 2021
    @ghost ghost closed this Mar 22, 2021
    @ghost
    Copy link

    ghost commented Mar 22, 2021

    Hi, @paterasMSFT. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee @anuchandy.

    @JackTn
    Copy link
    Member

    JackTn commented Jun 16, 2022

    Hi, @paterasMSFT. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.

    2 similar comments
    @JackTn
    Copy link
    Member

    JackTn commented Jun 16, 2022

    Hi, @paterasMSFT. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.

    @JackTn
    Copy link
    Member

    JackTn commented Jun 16, 2022

    Hi, @paterasMSFT. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.

    This pull request was closed.
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    DoNotMerge <valid label in PR review process> use to hold merge after approval NotReadyForReview <valid label in PR review process>It is in draft for swagger or not swagger PR
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    6 participants