Created specs for python 2 packages#3713
Created specs for python 2 packages#3713jhendrixMSFT merged 5 commits intoAzure:masterfrom D1v38om83r:bhbrahma-pr
Conversation
Automation for azure-sdk-for-pythonA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
|
@ravbhatnagar can you please review on behalf of the ARM team. I am introducing a new resource here that is practically the same as Azure automation Module (powershell), but for python. |
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
|
Can one of the admins verify this patch? |
Automation for azure-sdk-for-nodeA PR has been created for you: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
|
ping! |
| }, | ||
| "ModuleProperties": { | ||
| "properties": { | ||
| "isGlobal": { |
There was a problem hiding this comment.
bools are typically not recommended as they are less descriptive and dont allow for future expansion of states if needed.
There was a problem hiding this comment.
The property isGlobal is set in out data model as a boolean everywhere. Its not expected to change ever. The specs for Python 2 packages are practically the same a Powershell modules for consistency, except for paths.
| "type": "string", | ||
| "description": "Gets or sets the description." | ||
| }, | ||
| "isComposite": { |
There was a problem hiding this comment.
same comment for bool
There was a problem hiding this comment.
isComposite is never expected to change. The specs for Python 2 packages are practically the same a Powershell modules for consistency, except for paths.
| "x-ms-client-flatten": true, | ||
| "description": "Gets or sets the module update properties." | ||
| }, | ||
| "name": { |
There was a problem hiding this comment.
Is name of the resource really updatable?
There was a problem hiding this comment.
no, only the tag is updatable. Left in there for consistency with PowerShell modules.
There was a problem hiding this comment.
Consistency at the expense of something which doesnt work is not recommended. Please fix.
There was a problem hiding this comment.
I have removed the parameters which have no effect.
| "type": "string", | ||
| "description": "Gets or sets name of the resource." | ||
| }, | ||
| "location": { |
There was a problem hiding this comment.
location of azure resources is not updatbale.
There was a problem hiding this comment.
yes, that is correct. Left in there for consistency with PowerShell modules.
There was a problem hiding this comment.
same comment as above. lets fix this. And even fix powershell in a new api-version.
There was a problem hiding this comment.
I have removed the parameters which have no effect.
| "x-ms-client-flatten": true, | ||
| "description": "Gets or sets the module create properties." | ||
| }, | ||
| "name": { |
There was a problem hiding this comment.
name comes from the URL. It should be readonly in the request body
There was a problem hiding this comment.
Parameter name has been dropped
| ], | ||
| "description": "The parameters supplied to the create or update module properties." | ||
| }, | ||
| "ModuleCreateOrUpdateParameters": { |
There was a problem hiding this comment.
why is the same model no used for request and response? It helps in GET-PUT pipeline and makes it simpler to consume
|
Please be sure to review the fixes made to the powershell equivalent as there were some bugs in that swagger which made the "GetContent" API not work, see the history. |
|
@D1v38om83r any update on ARM feedback? |
|
@D1v38om83r there is a merge conflict, can you please rebase your changes on top of master? |
|
@D1v38om83r ping |
Automation for azure-sdk-for-jsNothing to generate for azure-sdk-for-js |
|
@jhendrixMSFT the merge conflicts have been resolved |
|
@D1v38om83r thanks! Where are we with the ARM review? |
|
@D1v38om83r also has this service been deployed? |
|
@ravbhatnagar can you please take a look at the changes I made addressing your PR comments. |
|
Looking at the ARM feedback I think the only remaining issue is why is the same model not used for request and response. Can this be fixed? |
|
The request and response are too dissimilar, there is next to no overlap. It doesn't make sense to combine them. |
|
Thanks for the explanation this makes sense. Will merge EOD unless @ravbhatnagar has any objections. |
Swagger spec update for new feature. Python 2 package support in Azure Automation.
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