-
Notifications
You must be signed in to change notification settings - Fork 230
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 to tfplugin 5.2, map new protocol fields (v2) #349
Conversation
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.
Pretty much approved, super small nitpicks/curiosities
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.
Looks like version2
got rebased, so this PR needs to rebase on version2
.
rebased |
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.
I'm not seeing any new tests added for this code. I may have missed them (a lot of test files changed), but if not, is there any way for us to test this new functionality/
Borrows some core code from 23acb02cb846fd002e7a0b52904ee88019b33211
@paddycarver added some test coverage for the global func at attribute level, there isn't any existing coverage at the resource level, but I can add it if you think its warranted. |
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.
Requested two log statements that you may have missed comments on a week ago. Not a big deal. Feel free to push them and merge, or merge without them and we'll address them if it ever comes up. I just see potential for bugs that we could make debugging easier, but it's not really a blocker.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
No description provided.