We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ceOverrides
ceOverrides lets you do things like hard code a CE type for event returned by a function in its response:
apiVersion: extensions.triggermesh.io/v1alpha1 kind: Function metadata: name: order-event-classifier spec: runtime: python adapterOverrides: public: true ceOverrides: extensions: type: my.overridden.type entrypoint: endpoint code: | from random import randrange def endpoint(event, context): ...
This isn't visible in the CRD reference docs:
I've create this issue in this repo because AFAIU this is something that would come from the CRD OAS specs.
I'm working on a docs PR in parallel, I'm interested to know exactly what else can be done with these ceOverrides.
Also, I wonder why the parameter is called extensions => shouldn't it be more like context. Is there a way to add CE extensions via ceOverrides?
extensions
context
The text was updated successfully, but these errors were encountered:
No branches or pull requests
ceOverrides
lets you do things like hard code a CE type for event returned by a function in its response:This isn't visible in the CRD reference docs:
I've create this issue in this repo because AFAIU this is something that would come from the CRD OAS specs.
I'm working on a docs PR in parallel, I'm interested to know exactly what else can be done with these
ceOverrides
.Also, I wonder why the parameter is called
extensions
=> shouldn't it be more likecontext
. Is there a way to add CE extensions viaceOverrides
?The text was updated successfully, but these errors were encountered: