Skip to content

Conversation

negz
Copy link
Member

@negz negz commented Aug 5, 2025

Description of your changes

Fixes #137

I don't think this would've ever worked if passed a RunFunctionRequest due to the way field presence works in most protobuf messages. In practice I can't think why req would ever be a Struct and not a RunFunctionRequest.

CC @bobh66 has this been working for you? Looks like you added this and I reviewed it, but I missed that req wouldn't be a struct in practice.

I have:

I don't think this would've ever worked if passed a RunFunctionRequest
due to the way field presence works in most protobuf messages. In
practice I can't think why req would ever be a Struct and not a
RunFunctionRequest.

Signed-off-by: Nic Cope <[email protected]>
@negz negz requested a review from bobh66 as a code owner August 5, 2025 21:19
Copy link
Collaborator

@bobh66 bobh66 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't remember why I added this and I can't think of a place we use it, but this looks more reasonable.

@negz negz merged commit b598b87 into crossplane:main Aug 6, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Field apiextensions.fn.proto.v1.RunFunctionRequest.credentials does not have presence when "resource.get_credentials()" called.
2 participants