You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by pc...@apache.org on 2021/11/25 12:47:50 UTC
[camel-k] branch main updated (fef0e61 -> f66d10d)
This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git.
from fef0e61 fix(build): default jitpack to main
new 0d26080 doc: no CLI integration run
new f66d10d fix(lint): godot complain
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/modules/ROOT/pages/running/running.adoc | 48 +++++++++++++++++++++++++++-
pkg/util/jitpack/jitpack.go | 6 ++--
2 files changed, 50 insertions(+), 4 deletions(-)
[camel-k] 02/02: fix(lint): godot complain
Posted by pc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit f66d10d47c9dc54bb7f151413df97a88ef237446
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Thu Nov 25 11:08:52 2021 +0100
fix(lint): godot complain
---
pkg/util/jitpack/jitpack.go | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/pkg/util/jitpack/jitpack.go b/pkg/util/jitpack/jitpack.go
index 62cd5c9..e5162fa 100644
--- a/pkg/util/jitpack/jitpack.go
+++ b/pkg/util/jitpack/jitpack.go
@@ -24,13 +24,13 @@ import (
)
const (
- // RepoURL is the Jitpack repository url
+ // RepoURL is the Jitpack repository url.
RepoURL = "https://jitpack.io"
- // DefaultVersion is the default branch/version to use
+ // DefaultVersion is the default branch/version to use.
DefaultVersion = "main-SNAPSHOT"
)
-// ToDependency converts a jitpack dependency into Dependency struct
+// ToDependency converts a jitpack dependency into Dependency struct.
func ToDependency(dependencyID string) *maven.Dependency {
gav := ""
[camel-k] 01/02: doc: no CLI integration run
Posted by pc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit 0d26080e7c6a7392d0e34aaa589d12ea915458a3
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Thu Nov 25 10:44:18 2021 +0100
doc: no CLI integration run
---
docs/modules/ROOT/pages/running/running.adoc | 48 +++++++++++++++++++++++++++-
1 file changed, 47 insertions(+), 1 deletion(-)
diff --git a/docs/modules/ROOT/pages/running/running.adoc b/docs/modules/ROOT/pages/running/running.adoc
index 93f655f..bd83d15 100644
--- a/docs/modules/ROOT/pages/running/running.adoc
+++ b/docs/modules/ROOT/pages/running/running.adoc
@@ -55,4 +55,50 @@ kamel logs hello
[[dev-mode-integration]]
== Running an Integration in Development mode
-Camel K provide a very nice **dev mode** feature that will allow you to apply any change to your Integration code reactively. Check out the xref:running/dev-mode.adoc[Camel K dev mode]
\ No newline at end of file
+Camel K provide a very nice **dev mode** feature that will allow you to apply any change to your Integration code reactively. Check out the xref:running/dev-mode.adoc[Camel K dev mode]
+
+[[no-cli-integration]]
+== Running an Integration without CLI
+
+You can run your integration also if you have no CLI available. `kamel` CLI manages a lot of fancy features but you can create an Integration Custom Resource (see the xref:apis/camel.adoc[API section] related to Integration) with all the configuration expected to run your application.
+
+As an example, let's get the result of a **dry run** for a sample route:
+
+```
+kamel run Sample.java -o yaml
+```
+
+It will return the expected Integration custom resource (you can type it manually according to the specification linked above):
+
+```
+apiVersion: camel.apache.org/v1
+kind: Integration
+metadata:
+ creationTimestamp: null
+ name: my-integration
+ namespace: default
+spec:
+ sources:
+ - content: "
+ import org.apache.camel.builder.RouteBuilder;
+ public class Sample extends RouteBuilder {
+ @Override
+ public void configure()
+ throws Exception {
+ from(\"timer:tick\")
+ .log(\"Hello Integration!\");
+ }
+ }"
+ name: Sample.java
+status: {}
+```
+
+We can save this custom resource in a yaml file, ie, `my-integration.yaml`. Once done, we can run the integration storing the Integration custom resource, via `kubectl`, UI, API call or whichever mean we have to call our Kubernetes cluster. In our example, we'll do this through `kubectl` CLI:
+
+```
+kubectl apply -f my-integration.yaml
+...
+integration.camel.apache.org/my-integration created
+```
+
+The operator will now take care to run the Integration accordingly.