Skip to content

Conversation

@rajshah11
Copy link
Contributor

@rajshah11 rajshah11 commented Feb 10, 2018

This PR moves ManagementGroups out of the Resources folder

Related PRs havings the specs and changes

Specs PRs

#2345
#2094
#1671

All minor changes

https://github.com/Azure/azure-rest-api-specs/pulls?q=is%3Apr+is%3Aclosed+author%3Arajshah11

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

@AutorestCI
Copy link

AutorestCI commented Feb 10, 2018

Automation for azure-sdk-for-python

A PR has been created for you:
Azure/azure-sdk-for-python#1968

@AutorestCI
Copy link

AutorestCI commented Feb 10, 2018

Automation for azure-sdk-for-go

Swagger to SDK encountered a Subprocess error: (azure-sdk-for-go)

Command: profileBuilder -s list -l ./profiles/2017-03-09/defintion.txt -name 2017-03-09
Finished with return code 127
and output:

/bin/sh: 1: profileBuilder: not found

@shahabhijeet
Copy link
Contributor

FYI @fearthecowboy this was already merged and approved earlier.

@rajshah11
Copy link
Contributor Author

Related PRs havings the specs and changes

Specs PRs

#2345
#2094
#1671

All minor changes

https://github.com/Azure/azure-rest-api-specs/pulls?q=is%3Apr+is%3Aclosed+author%3Arajshah11

@rajshah11
Copy link
Contributor Author

@fearthecowboy made this commit to incorporate the changes suggested for the earlier swagger in the latest one too.

@fearthecowboy
Copy link
Contributor

I'm concerned about the errors reported, and the impact it has on generation of existing SDKs.

//CC: @lmazuel -- I'm assuming this impacts you too?

@lmazuel
Copy link
Member

lmazuel commented Feb 12, 2018

@fearthecowboy I fixed the Readme in this PR, thanks for mentionning me :). This client has not been released yet, so moving it outside of resources is not a problem for Python.
@marstr should double-check Go as well.

@rajshah11
Copy link
Contributor Author

@fearthecowboy The errors are caused by the resources folder and they were there before as well. I think they have to fix their SDKs and it's one of the reasons why we eventually decided to move out of the folder.

@lmazuel Thanks for fixing the python settings in the managementgroups readme

@fearthecowboy
Copy link
Contributor

I'm ok with this; if @marstr is good for go then I can commit it.

Please also specify `--go-sdk-folder=<path to the root directory of your azure-sdk-for-go clone>`.

``` yaml $(tag)=='package-2017-08' && $(go)
output-folder: $(go-sdk-folder)/services/managementgroups/mgmt/2017-08-31-preview/managementgroups
Copy link
Member

Choose a reason for hiding this comment

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

The Go SDK has already shipped these clients to the former locations, as seen here:
Azure/azure-sdk-for-go@21b6814

Seeing as this would cause a breaking change for us, I'd like to leave the output-folder portion alone. Mind changing these to their old values?

Copy link
Contributor Author

@rajshah11 rajshah11 Feb 12, 2018

Choose a reason for hiding this comment

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

Done. However, I can keep the new paths for the later api versions right? Thanks!

@azuresdkciprbot
Copy link

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/managementgroups/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

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

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

Please also specify `--go-sdk-folder=<path to the root directory of your azure-sdk-for-go clone>`.

``` yaml $(tag)=='package-2017-11' && $(go)
output-folder: $(go-sdk-folder)/services/managementgroups/mgmt/2017-11-01-preview/managementgroups
Copy link
Member

Choose a reason for hiding this comment

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

Sorry I wasn't specific enough, please make this change to all of the go packages that you're modifying. :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done. Thanks

@azuresdkciprbot
Copy link

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/managementgroups/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

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

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@marstr
Copy link
Member

marstr commented Feb 13, 2018

My approval is limited to acknowledging that the paths in which these packages will be released has not changed for Go.

Copy link
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.

This is just a move,

@fearthecowboy fearthecowboy merged commit 4dec5ea into Azure:master Feb 13, 2018
mccleanp pushed a commit that referenced this pull request Mar 23, 2022
Microsoft.Provider Hub GA api version
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.

7 participants