-
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
[ACR] Add "19-05-01" GA specification for Microsoft.ContainerRegistry #5854
[ACR] Add "19-05-01" GA specification for Microsoft.ContainerRegistry #5854
Conversation
Automation for azure-sdk-for-jsA 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: |
Automation for azure-sdk-for-pythonEncountered a Subprocess error: (azure-sdk-for-python)
Command: python ./scripts/multiapi_init_gen.py azure-mgmt-containerregistry Traceback (most recent call last):
File "./scripts/multiapi_init_gen.py", line 22, in <module>
import azure.common
ModuleNotFoundError: No module named 'azure'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./scripts/multiapi_init_gen.py", line 26, in <module>
import azure.common
ModuleNotFoundError: No module named 'azure' |
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Can one of the admins verify this patch? |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaEncountered a Subprocess error: (azure-sdk-for-java)
Command: ['/usr/local/bin/autorest', '/tmp/tmpizm0bk8b/rest/specification/containerregistry/resource-manager/readme.md', '--perform-load=false', '--swagger-to-sdk', '--output-artifact=configuration.json', '--input-file=foo', '--output-folder=/tmp/tmpcui6pzj4'] AutoRest code generation utility [version: 2.0.4283; node: v8.12.0]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Failure:
Error: Unable to start AutoRest Core from /root/.autorest/@microsoft.azure_autorest-core@2.0.4373/node_modules/@microsoft.azure/autorest-core
Error: Unable to start AutoRest Core from /root/.autorest/@microsoft.azure_autorest-core@2.0.4373/node_modules/@microsoft.azure/autorest-core
at main (/opt/node_modules/autorest/dist/app.js:232:19)
at <anonymous>
/root/.autorest/@microsoft.azure_autorest-core@2.0.4373/node_modules/@microsoft.azure/autorest-core/dist/app.js:33
autorest_core_1.Shutdown();
^
ReferenceError: autorest_core_1 is not defined
at process.on (/root/.autorest/@microsoft.azure_autorest-core@2.0.4373/node_modules/@microsoft.azure/autorest-core/dist/app.js:33:5)
at emitOne (events.js:121:20)
at process.emit (events.js:211:7)
at process.emit (/node_modules/source-map-support/source-map-support.js:439:21)
fs.js:612
return binding.close(fd);
^
Error: EBADF: bad file descriptor, close
at Object.fs.closeSync (fs.js:612:18)
at StaticVolumeFile.shutdown (/opt/node_modules/autorest/dist/static-loader.js:352:10)
at StaticFilesystem.shutdown (/opt/node_modules/autorest/dist/static-loader.js:406:17)
at process.exit.n [as exit] (/opt/node_modules/autorest/dist/static-loader.js:169:11)
at printErrorAndExit (/node_modules/source-map-support/source-map-support.js:423:11)
at process.emit (/node_modules/source-map-support/source-map-support.js:435:16)
at process._fatalException (bootstrap_node.js:391:26) |
REST Spec PR 'Azure/azure-rest-api-specs#5854' REST Spec PR Author 'ankurkhemani' REST Spec PR Last commit
9ce56f2
to
9f4f2fd
Compare
REST Spec PR 'Azure/azure-rest-api-specs#5854' REST Spec PR Author 'ankurkhemani' REST Spec PR Last commit
@ankurkhemani - The new api-version does not contain many of the APis in the previous API version. Not sure why is this. Typically, all older APis are present in the latest api-version along with any additions or updates to existing. That way customer can move to the latest api-version and use all the functionality offered by your service. Please feel free to schedule a 30 min sync to close on this review quicker. |
8c6ac68
to
bdad522
Compare
@ravbhatnagar Those must be the Tasks APIs which are not part of this API version? Anyways, I will schedule a meeting to review these changes. |
@ravbhatnagar Can you help me understand why is the CI failing for |
startbuild |
bf71018
to
1139213
Compare
@dsgouda @ravbhatnagar Can you please help me understand the CI fail for |
@sergey-shandar please take a look |
REST Spec PR 'Azure/azure-rest-api-specs#5854' REST Spec PR Author 'ankurkhemani' REST Spec PR Last commit
Automation for azure-sdk-for-netA PR has been created for you: |
3 changes in this new api-version
|
@ravbhatnagar @sergey-shandar As discussed, I have added the enum for retention policy status. Also, created a work item #4672516 to track cross-api scenarios as mentioned by @ravbhatnagar Can you please help me with the CI here and get this PR merged? Also need to generate the python sdk. Thanks! |
REST Spec PR 'Azure/azure-rest-api-specs#5854' REST Spec PR Author 'ankurkhemani' REST Spec PR Last commit
Latest improvements:
Classic
SKU.RegistryProperties
and hence managed by CRUD on registry resource.(no new APIs added, two APIs deprecated)
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.