func
func copied to clipboard
knative
Samples (Templates)
Samples can be extremely helpful for first-time users of Knative functions so that they can
See them in action Understanding the Syntax and Structure Learning Best Practices Samples Exploring Use Cases Bootstrapping Development: Troubleshooting and Debugging
Some exmaples could be: Hello World: Basic samples that showcase the simplest form of a Knative function, one that respond for cloud event and one for http call and returns a "Hello, World!" response.
Data Processing: Samples that demonstrate how to process data using Knative functions. This can include tasks such as transforming data, aggregating information, or running calculations.
Image Processing: Examples that show how to perform image processing tasks using Knative functions. This can involve resizing images, applying filters, or extracting metadata.
Webhooks and Event-driven Workflows: Samples that illustrate how to create webhook endpoints and integrate Knative functions into event-driven workflows. These can include receiving GitHub notifications, handling HTTP events, or responding to messages from message brokers like Kafka or RabbitMQ.
Integration with External Services: Samples that demonstrate how to integrate Knative functions with external services, such as calling external APIs, interacting with databases, or sending notifications.
MetaController: Out of the box way functions can be used.
Updated Telegram demo Future: Event Streaming and Processing?
Machine Learning?
Chatbots and Voice Assistants ?
I agree this would be quite helpful. Ideally, where would these tutorial samples live?
could we create a different folder/repo under func? Thank you, -N
On Tue, 23 May 2023 at 09:32, Luke Kingland @.***> wrote:
I agree this would be quite helpful. Ideally, where would these tutorial samples live?
— Reply to this email directly, view it on GitHub https://github.com/knative/func/issues/1741#issuecomment-1559368803, or unsubscribe https://github.com/notifications/unsubscribe-auth/AISZCFFEN4XCLY7ZUK3XAYDXHS36RANCNFSM6AAAAAAYENFONA . You are receiving this because you authored the thread.Message ID: @.***>
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
That should probably be linked form main website samples docs eventually? https://knative.dev/docs/samples/
Also write knative blog(s) about it? I think only func related knative blog article is https://knative.dev/blog/articles/workflow-as-function-flow/ ?
I'm upgrading this to an Epic, with the expectation we'll create an individual issue for all or most of the samples suggested above.
I would prefer if this could be done in lock-step with the offical Functions Manual, such that a cruise through the manual from start-to-finish would also be augmented by samples of increasing complexity.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
@lkingland: Reopened this issue.
In response to this:
/reopen
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
![knative-prow[bot] avatar](https://avatars.githubusercontent.com/in/183726?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.