-
Notifications
You must be signed in to change notification settings - Fork 249
Issue-3938 Upgrade the Knative custom functions to have visibility over the returned status code and headers #3939
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
Open
oEscal
wants to merge
47
commits into
apache:main
Choose a base branch
from
oEscal:feature/3938
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
47 commits
Select commit
Hold shift + click to select a range
02fadd7
extended knative custom functions to support headers and query params
oEscal 515c491
code for returning REST custom function headers, status code, and to …
oEscal 153b334
Merge branch 'main' into feature/3936
oEscal f05f97b
Merge branch 'feature/knative-headers' into feature/3938
oEscal f045a43
code for returning Knative custom function headers, status code, and …
oEscal 7a5ae12
Merge branch 'main' into feature/knative-headers
oEscal ebde233
added the header and query arguments feature in knative for POSTs as …
oEscal c1f4e7a
small fix on the AbstractParamsDecorator
oEscal b09d8ff
Merge branch 'main' into feature/3938
oEscal c0d0fa2
Merge branch 'feature/3936' into feature/3938
oEscal 0bba1b5
merge updates
oEscal f981ecd
Merge branch 'main' into feature/knative-headers
oEscal 61e5ecb
Merge branch 'main' into feature/3936
oEscal 1728867
fixed style
oEscal c746a4e
Merge branch 'feature/3936' into feature/3938
oEscal 08ff33d
fixed style
oEscal f340c45
FAIL_ON_STATUS_ERROR_PARAMETER_NAME default for knative
oEscal 0d27227
fixed failing tests and format
oEscal a2eb1a4
Merge branch 'feature/knative-headers' into feature/3938
oEscal 8d90e4b
fixed OperationTests and format
oEscal 033521a
small fix for the tests
oEscal db2e0e7
formatting
oEscal 7fbc99b
Merge branch 'feature/knative-headers' into feature/3938
oEscal 736dd68
Merge branch 'main' into feature/3938
oEscal d75081a
small fix
oEscal ec21e7b
fix extractJsonNodeValue
oEscal a0374d9
small fix because of states that share the same execution scope (e.g.…
oEscal c05d384
merge with main
oEscal 3ded6c6
formatting issues
oEscal ad6c659
fixed checkStatusCode() call to still work with .statusCode
oEscal 36cc08d
fix RestWorkItemHandlerTest.java
oEscal f13a9e6
unit tests
oEscal 8c9f038
merge with pr 3937
oEscal bdb5419
Merge branch 'apache:main' into feature/3936
oEscal 8d65650
Merge branch 'apache:main' into feature/3938
oEscal b5e6832
some of the reviewer requests
oEscal 4da423e
requested restructure
oEscal ad843d2
answer the reviewers comments and IT test
oEscal f60f723
Update kogito-serverless-workflow/kogito-serverless-workflow-rest-run…
oEscal bced3b3
Merge branch 'main' into feature/3938
oEscal d476723
Merge branch 'feature/3936' into feature/3938
oEscal c0fdab3
going to the previous code version and updating the knative result ha…
oEscal cda741f
going back to defining headers and query params
oEscal 70e17f0
Merge branch 'apache:main' into feature/3938
oEscal 6bf4218
Change header and query prefix back to private access
oEscal 481b736
improve PlainJsonKnativeParamsDecorator implementation
oEscal 8d9b8b2
Merge branch 'apache:main' into feature/3938
oEscal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
Why do you need to do that?
How is this change related with the issue description?
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 think this was a leftover from the previous implementation where I was not considering the $WORKFLOW variable yet. However, this should be added to the Knative custom function to give control to the developer over the status code, message, and headers. What do you think? Do I create another issue/PR for that?