-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Reorganization for config files [Not Ready For Merge] #1215
Conversation
I'm testing out generating the Azure Resource Schemas from this. More minor changes yet coming, I'm sure. |
@fearthecowboy I have questions if you don't mind:
Otherwise, looks good to me |
Hey @lmazuel Ideally, you (meaning Python, or any other 'enlightened' generator) woulnd't use the per-RP readme.md files. I've added a 'batch' mode to autorest (although I think we're going to refactor it a bit more yet), that can process a very large list of swagger files sequentially, and I think it'll be a lot more to your liking. (I'm using it for AzureResourceSchema generation). In the not too distant future, I think we're going to remove entirely the notion of 'composite' (or merged swagger docs) in favor of individual processing, and allow generators to 'merge' the generation artifacts however they wish (in the case of c#, that's where we'd generate a per-RP client 'sdk' ) The folder structure is intended to be pretty strict (a given RP can have stuff in any namespace, but the resources in a namespace should be only that namespace) |
To be sure I understand, the "batch" more:
|
@lmazuel -- Yes. Question: Is there ever a case where you want a merged client? (for an 'work-in-progress' example see https://github.com/Azure/azure-rest-api-specs/blob/702e7033580b6b6b0ab4749f6b8f2f497b997d62/profiles/ResourceSchemas.md ) |
@fearthecowboy All network in one client, compute+disk in one client (for instance). |
@lmazuel ok, I'm in the office tomorrow -- we should get together sometime in the morning if you're free. I need to make sure we know exactly how you're doing things 🍖 |
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.
Readme at the root of the repo needs update.
There seem to be 2 folders "Microsoft.Advisor" and "microsoft.advisor" in arm-advisor.
@@ -0,0 +1,87 @@ | |||
# Compute |
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.
should the folder for the new specs be named "resource-manager" or "resource-management"?
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.
Is there a definitive reason one way or the other?
I have no strong feelings one way or the other.
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.
Not really, I've seen us use management before, but I just searched around in the Azure docs online and they seem to refer to it as Azure Resource Manager, so let's go with manager. Thanks!
are all composite files going away with this change, I noticed https://github.com/Azure/azure-rest-api-specs/blob/reorg/specification/insights/compositeInsightsManagementClient.json ? |
@@ -28,7 +28,18 @@ These are the global settings for the Batch API. | |||
# common | |||
title: Batch | |||
description: Batch Client | |||
api-version: 2017-01-01.4.0 | |||
api-version: 2017-05-01.5.0 |
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.
Ohh nooo what are these ^M
characters?
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.
Windows and it's desperate attempt to get all CRLF when LF will do?
Lemme see if I can eliminate them.
@olydis, please ensure that all .md files under arm-* directories have the |
@dsgouda went for |
@veronicagg as @olydis mentioned we are starting off with actually marking all specs not under arm* directories of the repo as |
@dsgouda I think that's reasonable, we can tune it based on feedback, it's going to anyway be a subset of what we have today, so should be better. |
The CI build script for linter needs to be updated to exclude all jsons under *examples* directories |
@dsgouda Wouldn't this 3900abb#diff-32008d041c23a0732242a32942c339e4R115 cover that or do we need the changes somewhere else? |
Folks I see changes requested on this PR and I believe we're going to switch the new structure on Monday, so what that plan for this PR? |
@olydis, I think you had an action item on the VMSS swagger and where it's going to show up for Networking right? |
* Update MD Compute for Python * Group python together * Group Python again * Update Web Readme for Python * Update SQL MD for Python * Update Monitor Mgmt MD for Python * Update Monitor Data MD for Python * Update GraphRBAC MD for Python * Partial update of Network MD for Python * Update full Network for Python * Remove creation of Python from MD
* Fix selection of swagger * Fixing `
This is the reorganized layout for the specs repository.
Testing with this should being ASAP;