-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Move ManagementGroups out of Resources to a separate folder #2469
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
Move ManagementGroups out of Resources to a separate folder #2469
Conversation
Automation for azure-sdk-for-pythonA PR has been created for you: |
Automation for azure-sdk-for-goSwagger 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 /bin/sh: 1: profileBuilder: not found |
|
FYI @fearthecowboy this was already merged and approved earlier. |
Related PRs havings the specs and changesSpecs PRsAll minor changes |
|
@fearthecowboy made this commit to incorporate the changes suggested for the earlier swagger in the latest one too. |
|
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? |
|
@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. |
|
@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 |
|
I'm ok with this; if @marstr is good for |
…shah11/azure-rest-api-specs into management-groups-specs-move
| 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 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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!
|
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: File: 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 |
There was a problem hiding this comment.
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. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. Thanks
|
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: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
|
My approval is limited to acknowledging that the paths in which these packages will be released has not changed for |
fearthecowboy
left a comment
There was a problem hiding this 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,
Microsoft.Provider Hub GA api version
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
api-versionin the path should match theapi-versionin the spec).Quality of Swagger