You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am thinking we could provide the following two Kubernetes CRDs that can extend the features of Hukz:
Provider (Slack, Google Chat, Teams, Sendgrid etc) that defines the required fields of a specific provider like endpoints, auth, message structure etc.
Application (Dega, Kavach etc) that defines the message structure of the input messages.
Then we can deploy Consumer Resource of type Provider for each consumer. This provides mapping for the fields from the input message to desired provider object, endpoints, auth etc.
This way we don't have to hardcode any application-related or provider-related data into Hukz and can extend it to any application or provider.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am thinking we could provide the following two Kubernetes CRDs that can extend the features of Hukz:
Then we can deploy Consumer Resource of type Provider for each consumer. This provides mapping for the fields from the input message to desired provider object, endpoints, auth etc.
This way we don't have to hardcode any application-related or provider-related data into Hukz and can extend it to any application or provider.
Beta Was this translation helpful? Give feedback.
All reactions