Skip to content

Conversation

@estebanreyl
Copy link

@estebanreyl estebanreyl commented Aug 28, 2019

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:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps. **_- Definitely tried it, never seems to leave the "still working" screen. Will update when I try again tomorrow but every other validator has succeeded.

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:

  • Added support for most of our Blob end point API's
  • HEAD (General and For chunks), GET (General and For chunks), DELETE /v2/{name}/blobs/{digest}
  • POST (Mount from Repository), POST (Start upload) /v2/{name}/blobs/uploads/
  • PATCH , PUT, GET, DELETE /v2/{name}/blobs/uploads/{uuid} # Note uses some trickery to improve user experience as these require a Location link instead of parameters (As the parameters can only be obtained by parsing the Location link)
  • Added Support for OCI Manifests, Manifest Lists, and OCI Index. Models are defined for each.
  • Renamed many functions to use cleaner names.

Bugfixes:

  • Cleaned up the entire swagger file re-using parameters and definition references
  • Fixed improper use of 32 bit numbers for storing the size of certain items like layer sizes. Since some layers can exceed this size this resulted in inaccurate measurements.

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.

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Aug 28, 2019

In Testing, Please Ignore

[Logs] (Generated from ef66280, Iteration 7)

Warning .NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
  • No packages generated.
Warning Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
  • Warning preview/containerregistry/runtime/2019-07 [Logs]

@AutorestCI
Copy link

AutorestCI commented Aug 28, 2019

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@AutorestCI
Copy link

AutorestCI commented Aug 28, 2019

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

"$ref": "./examples/GetDockerRegistryV2Support.json"
}
},
"operationId": "CheckV2Support",
Copy link
Member

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

Copy link
Author

@estebanreyl estebanreyl Aug 28, 2019

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",
Copy link
Member

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",
Copy link
Member

Choose a reason for hiding this comment

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

same as above

}
}
},
"307": {
Copy link
Member

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": {}
Copy link
Member

Choose a reason for hiding this comment

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

empty response body?

Copy link
Author

@estebanreyl estebanreyl Aug 28, 2019

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.

@yungezz yungezz added the APIStewardshipBoard-ReviewRequested This should be reviewed by the Azure API Stewardship team in partnership with the service team. label Aug 28, 2019
@estebanreyl
Copy link
Author

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?

@estebanreyl
Copy link
Author

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.

@estebanreyl
Copy link
Author

estebanreyl commented Aug 30, 2019

I don't want to be pushy, but I am unfortunately running out of time here, any updates on this front?

@yungezz
Copy link
Member

yungezz commented Sep 2, 2019

Hi @johanste , could you pls help to review the PR? thanks.

@yungezz yungezz merged commit 255757f into Azure:master Sep 2, 2019
nschonni added a commit to nschonni/azure-rest-api-specs that referenced this pull request Sep 2, 2019
erich-wang pushed a commit that referenced this pull request Sep 3, 2019
* fix: cspell failures

Related to #7060

* fix: Additional spelling issues from #6902
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

APIStewardshipBoard-ReviewRequested This should be reviewed by the Azure API Stewardship team in partnership with the service team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants