Skip to content

[Hub Generated] Review request for Microsoft.CostManagement to add version stable/2019-10-01#7972

Merged
raych1 merged 8 commits intoAzure:masterfrom
shbha1:dev-cost-management-Microsoft.CostManagement-2019-10-01
Dec 27, 2019
Merged

[Hub Generated] Review request for Microsoft.CostManagement to add version stable/2019-10-01#7972
raych1 merged 8 commits intoAzure:masterfrom
shbha1:dev-cost-management-Microsoft.CostManagement-2019-10-01

Conversation

@shbha1
Copy link
Copy Markdown
Contributor

@shbha1 shbha1 commented Dec 13, 2019

If you are a MSFT employee you can view your work branch via this link.

Contribution checklist:

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@openapi-sdkautomation
Copy link
Copy Markdown

openapi-sdkautomation Bot commented Dec 13, 2019

azure-sdk-for-python - Release

️✔️ succeeded [Logs] [Expand Details]
  • ️✔️ Generate from a1552e4 with merge commit 040a211. SDK Automation 13.0.17.20191226.1
  • ️✔️azure-mgmt-costmanagement [Logs]  [Release SDK Changes]
    [build_package] /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
    [build_package]   warnings.warn(msg)
    [build_package] warning: no files found matching '*.py' under directory 'tests'
    [build_package] warning: no files found matching '*.yaml' under directory 'tests'
    [build_package] /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
    [build_package]   warnings.warn(msg)
    [build_package] warning: no files found matching '*.py' under directory 'tests'
    [build_package] warning: no files found matching '*.yaml' under directory 'tests'

@openapi-sdkautomation
Copy link
Copy Markdown

openapi-sdkautomation Bot commented Dec 13, 2019

azure-sdk-for-java - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link
Copy Markdown

openapi-sdkautomation Bot commented Dec 13, 2019

azure-sdk-for-net - Release

️✔️ succeeded [Logs] [Expand Details]

@openapi-sdkautomation
Copy link
Copy Markdown

openapi-sdkautomation Bot commented Dec 13, 2019

azure-sdk-for-js - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link
Copy Markdown

openapi-sdkautomation Bot commented Dec 13, 2019

azure-sdk-for-go - Release

⚠️ warning [Logs] [Expand Details]
  • ⚠️ Generate from a1552e4 with merge commit 040a211. SDK Automation 13.0.17.20191226.1
  • ⚠️costmanagement/mgmt/2018-05-31 [Logs
      No file is changed.
    • ⚠️costmanagement/mgmt/2019-01-01 [Logs
        No file is changed.
      • ️✔️costmanagement/mgmt/2019-10-01 [Logs]  [Release SDK Changes]
      • ⚠️preview/costmanagement/mgmt/2018-08-01-preview [Logs
          No file is changed.
        • ⚠️preview/costmanagement/mgmt/2019-03-01 [Logs
            No file is changed.

          @azuresdkci
          Copy link
          Copy Markdown
          Contributor

          Can one of the admins verify this patch?

          @azure-pipelines
          Copy link
          Copy Markdown

          Commenter does not have sufficient privileges for PR 7972 in repo Azure/azure-rest-api-specs

          @azure-pipelines
          Copy link
          Copy Markdown

          Azure Pipelines successfully started running 1 pipeline(s).

          @azure-pipelines
          Copy link
          Copy Markdown

          Azure Pipelines successfully started running 1 pipeline(s).

          @yungezz
          Copy link
          Copy Markdown
          Member

          yungezz commented Dec 17, 2019

          hi @shbha1 could you pls fix CI failure, then the PR ok to merge.

          @yungezz
          Copy link
          Copy Markdown
          Member

          yungezz commented Dec 19, 2019

          ping for update

          @azure-pipelines
          Copy link
          Copy Markdown

          Azure Pipelines successfully started running 1 pipeline(s).

          @azure-pipelines
          Copy link
          Copy Markdown

          Azure Pipelines successfully started running 1 pipeline(s).

          @azure-pipelines
          Copy link
          Copy Markdown

          Azure Pipelines successfully started running 1 pipeline(s).

          @shbha1
          Copy link
          Copy Markdown
          Contributor Author

          shbha1 commented Dec 19, 2019

          Please confirm if we can merge without fixing the code-style issue the recent check is complaining about.

          @shbha1
          Copy link
          Copy Markdown
          Contributor Author

          shbha1 commented Dec 20, 2019

          What is pending to get this PR merged? (given the check failing is not 'required' i'd like to proceed with the PR)

          @yungezz
          Copy link
          Copy Markdown
          Member

          yungezz commented Dec 23, 2019

          /azp run

          @azure-pipelines
          Copy link
          Copy Markdown

          Azure Pipelines successfully started running 3 pipeline(s).

          @yungezz
          Copy link
          Copy Markdown
          Member

          yungezz commented Dec 23, 2019

          @ArcturusZhang
          Copy link
          Copy Markdown
          Member

          hi @ArcturusZhang could you pls help to look at the GO SDK generation failure? thanks. https://dev.azure.com/azure-sdk/internal/_build/results?buildId=217896&view=logs&j=fae805ed-8bde-5aa7-6387-2396f34533f9&t=c2e6587e-d03c-5fa9-0378-bc3c21e64d38

          One example file is malformed. I wonder why other CI does not report this.

          @ArcturusZhang
          Copy link
          Copy Markdown
          Member

          And there are also a lot of field that is reported as

          model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
          

          I highly recommend you to add description or title for them. If it is by design, just ignore this.
          And autorest also reports some other warnings like this:

          OperationId should contain the verb: 'query' in:'Query_Usage'. Consider updating the operationId
          

          Conventionally, operationId should be a puralNoun_Verb form.

          @yungezz
          Copy link
          Copy Markdown
          Member

          yungezz commented Dec 24, 2019

          hi @ArcturusZhang could you pls help to look at the GO SDK generation failure? thanks. https://dev.azure.com/azure-sdk/internal/_build/results?buildId=217896&view=logs&j=fae805ed-8bde-5aa7-6387-2396f34533f9&t=c2e6587e-d03c-5fa9-0378-bc3c21e64d38

          One example file is malformed. I wonder why other CI does not report this.

          hi @raych1 could you pls help to have a look why malformed example isn't reported? Thanks.

          @raych1
          Copy link
          Copy Markdown
          Member

          raych1 commented Dec 24, 2019

          hi @ArcturusZhang could you pls help to look at the GO SDK generation failure? thanks. https://dev.azure.com/azure-sdk/internal/_build/results?buildId=217896&view=logs&j=fae805ed-8bde-5aa7-6387-2396f34533f9&t=c2e6587e-d03c-5fa9-0378-bc3c21e64d38

          One example file is malformed. I wonder why other CI does not report this.

          hi @raych1 could you pls help to have a look why malformed example isn't reported? Thanks.

          @yungezz , model validation works as expected which has the JSON format error reported on the last 2nd commit CI checks result.

          @azure-pipelines
          Copy link
          Copy Markdown

          Azure Pipelines successfully started running 1 pipeline(s).

          @shbha1
          Copy link
          Copy Markdown
          Contributor Author

          shbha1 commented Dec 26, 2019

          can we please merge the PR (the failing test says 'prettier check' - not required check failed).

          @raych1
          Copy link
          Copy Markdown
          Member

          raych1 commented Dec 27, 2019

          It's interesting that OAV doesn't report when the missing curly bracket is in the end. I logged an issue to track this.

          @raych1 raych1 requested a review from ArcturusZhang December 27, 2019 02:50
          @raych1
          Copy link
          Copy Markdown
          Member

          raych1 commented Dec 27, 2019

          @ArcturusZhang , you requested the changes, can you please review this again?

          @raych1 raych1 merged commit 040a211 into Azure:master Dec 27, 2019
          Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

          Labels

          None yet

          Projects

          None yet

          Development

          Successfully merging this pull request may close these issues.

          6 participants