[KeyVault] - Migrate Key Vault Admin package to Core V2#15881
[KeyVault] - Migrate Key Vault Admin package to Core V2#15881maorleger merged 17 commits intoAzure:mainfrom
Conversation
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
There was a problem hiding this comment.
Because core-client depends on core-rest-pipeline 1.0.3 which still references preview 11, we need to downgrade here as well.
Once we GA core-rest-pipeline 1.1.0 and move all the packages to it we should be able to bump everyone to preview 12 in unison
There was a problem hiding this comment.
Moved these here while Azure/autorest.typescript#1013 is investigated
|
/check-enforcer evaluate |
|
test comment |
|
/azp run js - keyvault - ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run js - keyvault - ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run js - keyvault - ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Oh wow! This is a lot more thought through than what we had. I appreciate it!
sadasant
left a comment
There was a problem hiding this comment.
No stones left unturned! Bravo :)
36a760d to
4dbb469
Compare
There was a problem hiding this comment.
Maor and I have talked about whether this is a breaking change. I don’t think so, but Let’s get @xirzec ‘s thoughts
There was a problem hiding this comment.
There are 3 relatively minor breaking changes:
- Optional property
modewas removed fromretryOptionssince it only ever had a single enum value and was never used. handleRedirectswas removed fromredirectOptions, as the policy can now be controlled by removing it from the pipeline or settingmaxRedirectsto 0.keepAliveOptionswere removed. Keep alive can be disabled on a per-request basis withdisableKeepAlive.
These were all fairly niche options that tended to be used internally by our clients rather than set by consumers, but since we did expose them, we should consider what versioning implication this poses.
Alongside the change to remove _response, a strict semver interpretation would be to major version the package, but debatably a minor bump could be sufficient. /cc @chradek @ramya-rao-a @jeremymeng - I think we should have broad agreement on what our policy is here.
There was a problem hiding this comment.
I do plan to merge this PR, but leaving this conversation open if folks want to chime in. I'll also add it to the list of team meeting topics I have here 👍
There was a problem hiding this comment.
Since this package is still a beta I am less worried about it and don't think the discussion is blocking this PR
There was a problem hiding this comment.
Can we log an issue to ensure the discussion is continued and we come to a conclusion before this package goes GA?
jeremymeng
left a comment
There was a problem hiding this comment.
Did you re-generate from swagger? I am wondering why there isn't user agent related changes in generated code as we have seen in https://github.com/Azure/azure-sdk-for-js/pull/15777/files#diff-7a8e7d3e28eff9b33911029639e9b1582d1a692a0e39893e9fc6970916506c02
4252827 to
d651fd1
Compare
xirzec
left a comment
There was a problem hiding this comment.
Nice work on this! Very clean upgrade.
There was a problem hiding this comment.
Since this package is still a beta I am less worried about it and don't think the discussion is blocking this PR
What
KeyVaultBackupClientandKeyVaultAccessControlClientto core CAE@azure/core-lroversion to 1.0.6Why
This PR proves out two important things: it demonstrates that core continuous access evaluation works for both container
registry (already done) and Key Vault (this PR). It also demonstrates the migration path for Core V2 for Key Vault.
The change to core-lro addresses an issue where core-lro was incorrectly depending on core-http (#15880) That has been fixed on 1.0.6
and allows package owners to migrate to core-rest-pipeline and remove core-http without seeing build breaks.
Resolves #15522
Resolves #14306