-
Notifications
You must be signed in to change notification settings - Fork 165
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
update SDK to track2 in UpdateAPIIPEarly #3579
Conversation
268c7d9
to
91c8b15
Compare
Please rebase pull request. |
91c8b15
to
7bef6bd
Compare
7bef6bd
to
6257519
Compare
6257519
to
a909b39
Compare
/azp run ci,e2e |
Azure Pipelines successfully started running 2 pipeline(s). |
a909b39
to
729a019
Compare
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.
Thank you for this. No clear blockers, but I left some questions and some minor suggestions in case you can answer.
Thank you a lot.
729a019
to
3924fdc
Compare
/azp run ci,e2e |
Azure Pipelines successfully started running 2 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.
LGTM! Thank you @bitoku for the clarifications and applying the optional suggestions. Great work! 🚀
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.
LGTM, great work!
Which issue this PR addresses:
Fixes a part of https://issues.redhat.com/browse/ARO-4665 and https://issues.redhat.com/browse/ARO-7316
What this PR does / why we need it:
It contains three changes.
PublicIPAddresses
track2 SDK.updateAPIIPEarly
use track2 SDK.retryOption
to track2 SDKs.For
retryOption
see https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/azcore@v1.11.1/policy#RetryOptions and https://learn.microsoft.com/en-us/azure/developer/go/azure-sdk-core-concepts#http-pipeline-flowThe reason for creating new methods instead of modifying the current ones is to make the impact of each change as small as possible.
Test plan for issue:
unittest for updateAPIIPEarly.
test cluster installation in local.
e2e
Is there any documentation that needs to be updated for this PR?
tech debt cleanup N/A
How do you know this will function as expected in production?
cluster installation test