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 s3 bucket sink #5

Merged
merged 1 commit into from
Oct 2, 2024
Merged

Conversation

matzew
Copy link
Contributor

@matzew matzew commented Oct 2, 2024

Changes

  • as per title

/kind

Fixes #

Release Note


Docs


Copy link

knative-prow bot commented Oct 2, 2024

@matzew: The label(s) kind/<kind> cannot be applied, because the repository doesn't have them.

In response to this:

Changes

  • as per title

/kind

Fixes #

Release Note


Docs


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-sigs/prow repository.

Copy link
Contributor

@christophd christophd left a comment

Choose a reason for hiding this comment

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

The sink-connector has mixed a few things coming from a source-connector (e.g. in kn-connector-source.yaml which should rather follow the concepts of kn-connector-sink.yaml).

Please have a look into log-sink connector as an example or use the Maven archetype for sink connectors to generate the project

mvn archetype:generate \
 -DarchetypeGroupId=dev.knative.eventing \
 -DarchetypeArtifactId=kn-connector-archetype-sink \
 -DarchetypeVersion=1.0-SNAPSHOT

<scope>test</scope>
</dependency>
<dependency>
<groupId>org.eclipse.jetty.ee10</groupId>
Copy link
Contributor

Choose a reason for hiding this comment

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

The dependency is not required anymore as we have pinned the version in dependencyManagement in parent POM

# Knative Camel component
camel.component.knative.environmentPath=classpath:knative.json

camel.component.knative.ceOverride[ce-type]={{kn.connector.ce.override.type:dev.knative.connector.event.aws-s3}}
Copy link
Contributor

Choose a reason for hiding this comment

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

these ceOverrides are not required for the sink

metadata:
name: kn-connector-aws-s3-sink
spec:
source:
Copy link
Contributor

Choose a reason for hiding this comment

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

source should be the Knative Broker

apiVersion: camel.apache.org/v1
kind: Kamelet
name: aws-s3-sink
sink:
Copy link
Contributor

Choose a reason for hiding this comment

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

sink should be the aws-s3-sink Kamelet

Signed-off-by: Matthias Wessendorf <[email protected]>
@matzew
Copy link
Contributor Author

matzew commented Oct 2, 2024

I used the archetype now as:

mvn archetype:generate \
 -DarchetypeGroupId=dev.knative.eventing \
 -DarchetypeArtifactId=kn-connector-archetype-sink \
 -DarchetypeVersion=1.0-SNAPSHOT \
 -DartifactId=aws-s3-sink \
 -Dkamelet-name=aws-s3 \
 -Dcomponent-name=aws2-s3

the pom.xml diff is manually - I just added the sink module.

I reverted the change from the archetype since it was adding new lines after each existing line. Was very verbose

@christophd
Copy link
Contributor

christophd commented Oct 2, 2024

I reverted the change from the archetype since it was adding new lines after each existing line. Was very verbose

yes, Maven archetype process goes wild on formatting the existing POM. Revert and adding the module manually is the best option for now. thanks

Copy link
Contributor

@christophd christophd left a comment

Choose a reason for hiding this comment

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

LGTM now

@@ -0,0 +1,4 @@
|===
|Property |Required |EnvVar |Description
Copy link
Contributor

Choose a reason for hiding this comment

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

consider running mvn package once before the PR, so the docs get generated

Copy link

knative-prow bot commented Oct 2, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christophd, 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 merged commit dce829d into knative-extensions:main Oct 2, 2024
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants