-
Notifications
You must be signed in to change notification settings - Fork 842
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 data plane module #19554
ACR data plane module #19554
Conversation
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azacr - ci |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Should the path be something like this.
IMO |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azcontainerregistry - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
New SDKs should use remote test assets and not check in the recordings. Please see https://github.com/Azure/azure-sdk-tools/blob/main/tools/test-proxy/documentation/asset-sync/README.md#im-a-dev-who-uses-the-test-proxy-currently-how-do-i-externalize-my-recordings for more details.
You can also see an example of this being enabled for azqueue
in #19756
Resolved. |
@jhendrixMSFT I've resolved all CI failure. Could you help to review again? |
This is the first preview version of ACR data plane package. Most majority of the operations is auto-generated. Customizations are done by autorest directive. Manual code includes auth policy, client CTOR and blob upload operations.
Resolve: #19483