Skip to content
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

Adding apache camel k blog post #5992

Merged
merged 9 commits into from
May 27, 2024
Merged

Conversation

matzew
Copy link
Member

@matzew matzew commented May 23, 2024

Proposed Changes

  • Blog of Apache Camel K and Knative Eventing

@knative-prow knative-prow bot requested review from nainaz and snneji May 23, 2024 14:13
@knative-prow knative-prow bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label May 23, 2024
Copy link

netlify bot commented May 23, 2024

Deploy Preview for knative ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 9d94e0c
🔍 Latest deploy log https://app.netlify.com/sites/knative/deploys/66548e563423c500087550e7
😎 Deploy Preview https://deploy-preview-5992--knative.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Signed-off-by: Matthias Wessendorf <[email protected]>
@matzew matzew force-pushed the add_camel_k_eventing branch from db7059d to 0e63c95 Compare May 23, 2024 14:20
@matzew matzew closed this May 27, 2024
@matzew matzew reopened this May 27, 2024
@matzew
Copy link
Member Author

matzew commented May 27, 2024

close, reopen, since CLA check was wrongly failing

Copy link
Member

@creydr creydr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great to have a blog about this! 💪

Left some comments. Maybe you can also change from "we" to "you" (https://github.com/knative/docs/blob/main/contribute-to-docs/style-guide/voice-and-language.md#address-the-reader-as-you-not-we) 🤷

blog/docs/articles/knative-meets-apache-camel.md Outdated Show resolved Hide resolved
blog/docs/articles/knative-meets-apache-camel.md Outdated Show resolved Hide resolved
blog/docs/articles/knative-meets-apache-camel.md Outdated Show resolved Hide resolved
blog/docs/articles/knative-meets-apache-camel.md Outdated Show resolved Hide resolved
kind: Kamelet
apiVersion: camel.apache.org/v1
name: timer-source
properties:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe you add a quick note, that the properties field is specific for the referenced kind (from .spec.source.ref). As you later use the same for the Trigger filter (line 81 & 82)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a sentence below that example.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@knative-prow knative-prow bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 27, 2024
Comment on lines +81 to +82
properties:
type: com.corp.my.timer.source
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this necessary for a "sink" ?

Copy link
Member Author

@matzew matzew May 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, it is optional, w/o that it has a different CloudEvent type (org.apache....)

there is a bug in camel k, when reading from the broker. one MUST use proerties.type

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is sink though? isn't it using the given type already ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, sorry. I did not see which you commented on. This is (currently) required. I have filed a bug w/ them, last week

@dsimansk
Copy link
Contributor

/approve
/lgtm

/hold for other reviews

@knative-prow knative-prow bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 27, 2024
@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label May 27, 2024
Copy link

knative-prow bot commented May 27, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dsimansk, matzew

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 27, 2024
@dsimansk
Copy link
Contributor

@matzew one highlight idea. IMO it's a good candidate to add to "Featured Posts" section to promote it a bit more. I'd put it just below 1.14 release blog post. WDYT?

/cc @pierDipi @creydr

https://knative.dev/blog/#featured-posts

@knative-prow knative-prow bot requested review from creydr and pierDipi May 27, 2024 13:32
@knative-prow knative-prow bot removed the lgtm Indicates that a PR is ready to be merged. label May 27, 2024
@dsimansk
Copy link
Contributor

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label May 27, 2024
@matzew
Copy link
Member Author

matzew commented May 27, 2024

/unhold

@knative-prow knative-prow bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 27, 2024
@knative-prow knative-prow bot merged commit cb18e1e into knative:main May 27, 2024
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants