-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Move all packages that use core-http to use the newer Azure Core packages #15594
Closed
22 tasks done
Labels
Comments
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Jun 7, 2021
This was referenced Jun 7, 2021
ramya-rao-a
added
the
Client
This issue points to a problem in the data-plane of the library.
label
Jun 7, 2021
ghost
removed
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Jun 7, 2021
This was referenced Jun 17, 2021
[Azure Container Registry]Move the Azure Container Registry package to use core-rest-pipeline
#15822
Closed
For folks working on this, after regenerating code don't forget to remove the dependency on core-http and add a dependency on @azure/core-client (^1.0.0) and @azure/core-rest-pipeline (^1.1.0) in your |
This was referenced Jul 15, 2021
openapi-sdkautomation bot
pushed a commit
to AzureSDKAutomation/azure-sdk-for-js
that referenced
this issue
Aug 13, 2021
4 tasks
This was referenced Mar 17, 2022
4 tasks
3 tasks
xirzec
added a commit
that referenced
this issue
Jun 15, 2023
### Packages impacted by this PR `@azure/storage-queue` ### Issues associated with this PR Fixes #15813 Closes #15594 ### Describe the problem that is addressed by this PR This PR migrates storage-queue to the new core pipeline in the same way that storage-file-share was migrated. There are no changes to the public surface and existing recorded tests still pass. ### Provide a list of related PRs _(if any)_ #26102
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
We started out shipping the newer packages in November 2019 that all used the
@azure/core-http
package mainly that implemented pipelines and policies for making http requests. See the readme for core packages for more details.Earlier this year, we shipped Azure Core 2.0 for JS SDKs
In May 2021, we shipped a new version of our SDK generator that supports these newer core packages by default with an option to use the older core-http
This issue is to track the work needed to ensure all our packages have been upgraded to use the new Azure Core v2.
We documented one of the package moves in a wiki which you can refer to for changes you may want to do in the hand written layer of your package to avoid any breaking changes for your customers. See
core http
dependency migration tocore client
core rest pipeline
Packages that already use the newer Azure Core v2 packages, but should be upgraded to use the output of the latest version of our SDK generator
Packages that use the older core-http, but not the code generator and should upgrade to use the newer core packages
Packages that use the older core-http, have a convenience layer over generated code and should be upgraded to use the output of the latest version of our SDK generator. You most probably have a swagger/README.md file where you have configured the
use-extenstion
argument to a version of@autorest/typescript
. Update this to the latest beta version of https://www.npmjs.com/package/@autorest/typescript and re-generate your codeRest of the packages that are currently purely auto-generated and so will automatically get updated the next time there is a swagger update
Benefits of the move can be found in https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/core/core-rest-pipeline/documentation/core2.md
The text was updated successfully, but these errors were encountered: