Skip to content
This repository has been archived by the owner on Dec 15, 2021. It is now read-only.

Commit

Permalink
Update implementing-new-trigger.md (#1216)
Browse files Browse the repository at this point in the history
  • Loading branch information
saintmalik authored Jan 20, 2021
1 parent 579f848 commit 1c81cad
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/implementing-new-trigger.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Give appropriate and intutive name to the event source.
## Model the CRD spec
Once CRD is defined, you need to model the event source and its attributes as resource object spec. Please see [API conventions](https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md) for key attributes of Kubernetes API resource object. Except fot `Spec` part rest of the needed parts to define a Trigger are pretty similar to other Triggers.
Once CRD is defined, you need to model the event source and its attributes as resource object spec. Please see [API conventions](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md) for key attributes of Kubernetes API resource object. Except fot `Spec` part rest of the needed parts to define a Trigger are pretty similar to other Triggers.

For e.g below is the definition of [Kafka Trigger](https://github.com/kubeless/kafka-trigger/blob/master/pkg/apis/kubeless/v1beta1/kafka_trigger.go)

Expand Down

0 comments on commit 1c81cad

Please sign in to comment.