-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Estebanreyl/data plane 08 2019 #7060
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
Conversation
This reverts commit 18deb78.
In Testing, Please Ignore[Logs] (Generated from ef66280, Iteration 7)
|
Automation for azure-sdk-for-pythonNothing to generate for azure-sdk-for-python |
Automation for azure-sdk-for-goNothing to generate for azure-sdk-for-go |
|
Can one of the admins verify this patch? |
| "$ref": "./examples/GetDockerRegistryV2Support.json" | ||
| } | ||
| }, | ||
| "operationId": "CheckV2Support", |
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.
operationId naming convention: Resource_Action
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.
I've updated this for all items in question.
| "$ref": "./examples/GetManifest.json" | ||
| } | ||
| }, | ||
| "operationId": "GetManifest", |
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.
operationId naming convention: Resource_Action
| "consumes": [ | ||
| "application/vnd.docker.distribution.manifest.v2+json" | ||
| ], | ||
| "operationId": "CreateManifest", |
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.
same as above
| } | ||
| } | ||
| }, | ||
| "307": { |
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.
normally not put return code other than 2xx in swagger. need ARM feedback.
| } | ||
| }, | ||
| "responses": { | ||
| "200": {} |
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.
empty response body?
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.
That method doesn't return anything in fact. Only the status code is relevant. Adding an empty reponse body seems to bring a warning in oav.
|
Its not immediately evident to me why the pipeline tests may be failing. Looking at the results it seems like they crash on th semantic validation. Any ideas? |
...nerregistry/data-plane/Microsoft.ContainerRegistry/preview/2019-08-15/containerregistry.json
Outdated
Show resolved
Hide resolved
|
As a note there should be no need for an Azure REST API review board to review as described in: #6629 (comment) . This follows as the API is already in production. |
|
I don't want to be pushy, but I am unfortunately running out of time here, any updates on this front? |
|
Hi @johanste , could you pls help to review the PR? thanks. |
Related to Azure#7060
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
As a note a few linting issues could not be resolved as they are intrinsic in handling compatibility with docker or OCI's own expectations for registry API's I will also be following up in email as described in https://github.com/Azure/adx-documentation-pr/wiki/Swagger-Validation-Errors-Suppression
This is a Preview Release for the ACR runtime data-plane API specification
This should be a fully functional release to address: #6773. As an important note to this one, my internship is coming to an end next week and I still need to get this through before making a PR to the .NET SDK repository. I would really appreciate it if we could get this looked at quickly.
Changes:
Bugfixes:
All paths have been verified and the generated client has been tested as well in C#. This should ideally lead to a release of a fully functioning .NET SDK.