Skip to content

Api Management - Versions, Revisions and Releases#2295

Merged
fearthecowboy merged 4 commits into
Azure:masterfrom
darrelmiller:clean-versions
Jan 30, 2018
Merged

Api Management - Versions, Revisions and Releases#2295
fearthecowboy merged 4 commits into
Azure:masterfrom
darrelmiller:clean-versions

Conversation

@darrelmiller
Copy link
Copy Markdown
Member

@darrelmiller darrelmiller commented Jan 19, 2018

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • [] If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@azuresdkciprbot
Copy link
Copy Markdown

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/apimanagement/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 2
After the PR: Warning(s): 0 Error(s): 2

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@marstr marstr changed the base branch from current to master January 19, 2018 16:40
@marstr
Copy link
Copy Markdown
Member

marstr commented Jan 19, 2018

We made some updates in December, and moved back to working out of master. current is just a duplicate of master to allow for an easier transition. You can read more about all of the changes we made here: December 2017 Refactoring

Copy link
Copy Markdown
Contributor

@fearthecowboy fearthecowboy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks OK to me.

New APIs added -- requires ARM signoff by @ravbhatnagar

@fearthecowboy fearthecowboy added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jan 22, 2018
@fearthecowboy
Copy link
Copy Markdown
Contributor

FYI; the two validation errors are being addressed with suppressions in a different PR #2257

}
}
},
"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/apis/{apiId}/revisions": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is revision an ARM resource? Is is possible to get an individual revision?

@ravbhatnagar
Copy link
Copy Markdown
Contributor

Looks good. Just one question whether revisions is a resource and if its possible to get an individual revision.

@darrelmiller
Copy link
Copy Markdown
Member Author

@ravbhatnagar There is no .../revisions/{revisionId} operation because it would be redundant with .../apis/{apiId} as every API is also a revision. The .../revisions operation is simply a read-only concept used to drive a UI view. It is not a ARM Resource.

@ravbhatnagar
Copy link
Copy Markdown
Contributor

Signing off!

@ravbhatnagar ravbhatnagar added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jan 25, 2018
@darrelmiller
Copy link
Copy Markdown
Member Author

@fearthecowboy Could you push the big green button please?

@fearthecowboy fearthecowboy merged commit d062804 into Azure:master Jan 30, 2018
@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-ruby

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-python

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-ruby

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-python

@AutorestCI
Copy link
Copy Markdown

This commit was treated and no generation was made for Azure/azure-sdk-for-python

@AutorestCI
Copy link
Copy Markdown

Swagger to SDK encountered an unknown error: (Azure/azure-sdk-for-python)

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/github_tools.py", line 29, in exception_to_github
    yield context
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/github.py", line 180, in rest_handle_action
    return rest_pull_close(body, github_con, restapi_repo, sdk_pr_target_repo, sdkbase)
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/github.py", line 311, in rest_pull_close
    rest_pr.create_issue_comment("Was unable to create SDK %s PR for this closed PR.", sdkid)
TypeError: create_issue_comment() takes 2 positional arguments but 3 were given

@AutorestCI
Copy link
Copy Markdown

This commit was treated and no generation was made for Azure/azure-sdk-for-go

@AutorestCI
Copy link
Copy Markdown

Swagger to SDK encountered an unknown error: (Azure/azure-sdk-for-go)

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/github_tools.py", line 29, in exception_to_github
    yield context
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/github.py", line 180, in rest_handle_action
    return rest_pull_close(body, github_con, restapi_repo, sdk_pr_target_repo, sdkbase)
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/github.py", line 311, in rest_pull_close
    rest_pr.create_issue_comment("Was unable to create SDK %s PR for this closed PR.", sdkid)
TypeError: create_issue_comment() takes 2 positional arguments but 3 were given

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

Labels

ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants