update to v3 and move v2 to local sdk #1500
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
duytiennguyen-okta
force-pushed
the
OKTA-591377-update-to-go-sdk-v3
branch
from
3173caf to
5c10aa5
Compare
duytiennguyen-okta
force-pushed
the
OKTA-591377-update-to-go-sdk-v3
branch
from
5c10aa5 to
9f5bcef
Compare
duytiennguyen-okta
force-pushed
the
OKTA-591377-update-to-go-sdk-v3
branch
from
138fdf3 to
30e4042
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are upgrading from v2 to v3 of okta/okta-sdk-golang. Our strategy here is to avoid changing all sdk references at one time, putting us at risk of bugs, is to vendor local v2 and slowly remove those files as we switch over to v3.