lburgazzoli commented on issue #47: Route loaders should derive language from
'kamel run --language' #46
URL: https://github.com/apache/camel-k/pull/47#issuecomment-420532736
done
This is an automated message from the Apache
nicolaferraro commented on a change in pull request #48: Support set
integration name for kamel run
URL: https://github.com/apache/camel-k/pull/48#discussion_r216911437
##
File path: pkg/client/cmd/run.go
##
@@ -51,6 +52,7 @@ func NewCmdRun(rootCmdOptions *RootCmdOptions)
nicolaferraro commented on a change in pull request #47: Route loaders should
derive language from 'kamel run --language' #46
URL: https://github.com/apache/camel-k/pull/47#discussion_r216910691
##
File path:
runtime/jvm/src/test/java/org/apache/camel/k/jvm/RoutesLoadersTest.java
nicolaferraro commented on a change in pull request #47: Route loaders should
derive language from 'kamel run --language' #46
URL: https://github.com/apache/camel-k/pull/47#discussion_r216910492
##
File path: runtime/jvm/src/main/java/org/apache/camel/k/jvm/RoutesLoaders.java
#
nicolaferraro commented on a change in pull request #47: Route loaders should
derive language from 'kamel run --language' #46
URL: https://github.com/apache/camel-k/pull/47#discussion_r216910313
##
File path: runtime/jvm/src/main/java/org/apache/camel/k/jvm/Application.java
###
nicolaferraro commented on a change in pull request #47: Route loaders should
derive language from 'kamel run --language' #46
URL: https://github.com/apache/camel-k/pull/47#discussion_r216910580
##
File path: runtime/jvm/src/main/java/org/apache/camel/k/jvm/RoutesLoaders.java
#
nicolaferraro commented on a change in pull request #47: Route loaders should
derive language from 'kamel run --language' #46
URL: https://github.com/apache/camel-k/pull/47#discussion_r216910456
##
File path: runtime/jvm/src/main/java/org/apache/camel/k/jvm/RoutesLoader.java
##
oscerd opened a new pull request #48: Support set integration name for kamel run
URL: https://github.com/apache/camel-k/pull/48
fixes #40
This is an automated message from the Apache Git Service.
To respond to the message, ple
Github user oscerd closed the pull request at:
https://github.com/apache/camel/pull/2517
---
kyleabcha commented on issue #44: How to know a Component status at a time
URL: https://github.com/apache/camel-k/issues/44#issuecomment-420514108
thank you. the issue is closed.
This is an automated message from the Apache Gi
lburgazzoli opened a new issue #46: Route loaders should derive language from
"kamel run --language"
URL: https://github.com/apache/camel-k/issues/46
Route loaders determine the language to use by looking at the file extension
only so it discards any value eventually set from by `kamel run
dmvolod commented on issue #43: Unable to reinstall the operator
URL: https://github.com/apache/camel-k/issues/43#issuecomment-420513538
@nicolaferraro , thanks I will take a look.
This is an automated message from the Apache
oscerd commented on issue #40: Support set integration name for kamel run
URL: https://github.com/apache/camel-k/issues/40#issuecomment-420512966
Sure
This is an automated message from the Apache Git Service.
To respond to the
lburgazzoli opened a new issue #45: Support for multiple integration definitions
URL: https://github.com/apache/camel-k/issues/45
We can now deploy our routes by defining them in a single file and the using
the `kamel` command like:
kamel run MyRoutes.js
But it would be ni
oscerd closed issue #44: How to know a Component status at a time
URL: https://github.com/apache/camel-k/issues/44
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and
oscerd commented on issue #44: How to know a Component status at a time
URL: https://github.com/apache/camel-k/issues/44#issuecomment-420512774
Please ask on the users mailing list users at camel.apache.org
This is an automate
kyleabcha opened a new issue #44: How to know a Component status at a time
URL: https://github.com/apache/camel-k/issues/44
Hi,
I am having difficulty how to differ when a Component (DefaultComponent) is
deployed (NEW) or when it is just restarted or undeployed (REMOVED completely).
nicolaferraro opened a new issue #43: Unable to reinstall the operator
URL: https://github.com/apache/camel-k/issues/43
If trying to execute `kamel install` twice, the second installation fails
for a issue while trying to update the service:
```
Service "camel-k-operator" is inval
nicolaferraro commented on issue #41: Cannot deploy integration if not in the
"kamel" package
URL: https://github.com/apache/camel-k/issues/41#issuecomment-420448287
Fixed by #39.
This is an automated message from the Apache
nicolaferraro closed issue #41: Cannot deploy integration if not in the "kamel"
package
URL: https://github.com/apache/camel-k/issues/41
This is an automated message from the Apache Git Service.
To respond to the message, pl
nicolaferraro closed pull request #39: add support for non java integrations
URL: https://github.com/apache/camel-k/pull/39
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull
nicolaferraro opened a new issue #42: Add "make install-minishift" command
URL: https://github.com/apache/camel-k/issues/42
As explained in the readme, the procedure to do a local build and deploy is
complex. We should add a `make install-minishift` command to simplify it (and
update docum
nicolaferraro opened a new issue #41: Cannot deploy integration if not in the
"kamel" package
URL: https://github.com/apache/camel-k/issues/41
Integrations not using the "kamel" package (see `Sample.java` in the repo
root) cannot be run. The reason is that the package is in some way hardco
lburgazzoli edited a comment on issue #40: Support set integration name for
kamel run
URL: https://github.com/apache/camel-k/issues/40#issuecomment-420442166
Thre is also a problem when the file is located on a different directory
than the current one i.e. `runtime/examples/Sample.java` be
lburgazzoli commented on issue #40: Support set integration name for kamel run
URL: https://github.com/apache/camel-k/issues/40#issuecomment-420442166
Thre is also a problem when the file is located on a different directory
than the current one i,e `runtime/examples/Sample.java` becomes
`r
nicolaferraro commented on issue #40: Support set integration name for kamel run
URL: https://github.com/apache/camel-k/issues/40#issuecomment-420441434
I'll add also that the current mapping is trivial, e.g. `MyIntegration.java`
-> `myintegration`.
A better name would be `my-integra
nicolaferraro commented on issue #30: Manage dependencies
URL: https://github.com/apache/camel-k/issues/30#issuecomment-420440725
I think this is a problem we have in common with FaaS platforms, we should
investigate what they do to add dependencies to a function.
I'm thinking that t
lburgazzoli opened a new issue #40: Support set integration name for kamel run
URL: https://github.com/apache/camel-k/issues/40
the `kamel run` command determine the integration name using the integration
file name but it would be nice to let the user set the name of the integration
with a
lburgazzoli commented on issue #40: Support set integration name for kamel run
URL: https://github.com/apache/camel-k/issues/40#issuecomment-420439896
@oscerd do you mind having a look ?
This is an automated message from the A
nicolaferraro opened a new issue #38: Add uninstall command
URL: https://github.com/apache/camel-k/issues/38
It's would be nice to have an uninstall command which will remove all
camel-k artifacts (cluster-wide and project related). This will be useful for
development and update procedures
nicolaferraro opened a new issue #37: Improve user guide
URL: https://github.com/apache/camel-k/issues/37
We should document what options and scenarios are available for a end user
(from running "kamel run Source.java" on)
---
nicolaferraro opened a new issue #36: Document architecture
URL: https://github.com/apache/camel-k/issues/36
We should document the architecture:
- CRDs
- Operator and client, how they interact
- Build modes
- Publishing modes
- The deployment flow
---
nicolaferraro opened a new issue #35: Add roadmap information
URL: https://github.com/apache/camel-k/issues/35
We should add to the documentation a high level roadmap of the project (see
https://github.com/nicolaferraro/integration-operator).
---
nicolaferraro opened a new issue #34: Add dev mode
URL: https://github.com/apache/camel-k/issues/34
It would be nice to mix deployment with contexts and #33 to create a "kamel
run --dev Source.java" that:
- Deploys the integration with a sidecar strategy
- Waits for the deployment to
nicolaferraro opened a new issue #33: Add wait and log watch options
URL: https://github.com/apache/camel-k/issues/33
We should add a flag to "kamel run" to wait for the deployment to be
completed before returning ("–wait").
We should add a "kamel logs" command to display a integrati
nicolaferraro opened a new issue #32: Figure out how to deploy integrations on
plain Kubernetes
URL: https://github.com/apache/camel-k/issues/32
There's no embedded Docker registry. Are we going to create one?
Deployment through a builder sidecar is not a good option in a serverless
lburgazzoli commented on issue #30: Manage dependencies
URL: https://github.com/apache/camel-k/issues/30#issuecomment-420435170
Wondering if we start supporting only
- kamel run --dependency camel-mail Source.java
- Putting it direcly in spec->dependency->items by editing the custom
r
nicolaferraro opened a new issue #31: Allow buildless direct deploy
URL: https://github.com/apache/camel-k/issues/31
The general way of doing builds expects a build phase where a docker image
is generated.
In some cases, when there are no additional dependencies to load respect to
"
nicolaferraro opened a new issue #30: Manage dependencies
URL: https://github.com/apache/camel-k/issues/30
When the user executes "kamel run Source.java", he might be using some
components not available in camel-core.
In this case, the "kamel" script should create the resource as usu
GitHub user jamesmurf opened a pull request:
https://github.com/apache/camel/pull/2518
changed csv unmarshalling to only strip quotes if quoting is set to "true"
When unmarshalling a tsv file where the individual fields are not quoted,
the unmarshaller still tries to strip the quote
lburgazzoli closed pull request #29: Adding contributing guide
URL: https://github.com/apache/camel-k/pull/29
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (fro
GitHub user vrlgohel opened a pull request:
https://github.com/apache/camel/pull/2517
CAMEL-12785: ServletComponent ignores HttpBinding
We dropped the **httpBindingRef** in http common and servlet component some
time back. The Servlet Component had a regression where it wasn't takin
Github user PascalSchumacher closed the pull request at:
https://github.com/apache/camel/pull/2516
---
nicolaferraro opened a new pull request #29: Adding contributing guide
URL: https://github.com/apache/camel-k/pull/29
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub
nicolaferraro closed pull request #28: Bump Camel to version 2.22.1
URL: https://github.com/apache/camel-k/pull/28
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and
oscerd opened a new pull request #28: Bump Camel to version 2.22.1
URL: https://github.com/apache/camel-k/pull/28
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and u
nicolaferraro closed pull request #27: generate pom using go's xml encoder
URL: https://github.com/apache/camel-k/pull/27
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull r
nicolaferraro commented on issue #27: generate pom using go's xml encoder
URL: https://github.com/apache/camel-k/pull/27#issuecomment-420328636
Nice!
This is an automated message from the Apache Git Service.
To respond to the
We need your help to make the Apache Washington DC Roadshow on Dec 4th a
success.
What do we need most? Speakers!
We're bringing a unique DC flavor to this event by mixing Open Source
Software with talks about Apache projects as well as OSS CyberSecurity,
OSS in Government and and OSS Career
lburgazzoli closed pull request #26: Fix typo in print integration context
URL: https://github.com/apache/camel-k/pull/26
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull r
dmvolod commented on issue #26: Fix typo in print integration context
URL: https://github.com/apache/camel-k/pull/26#issuecomment-420294715
Hope, this is correct fix :)
This is an automated message from the Apache Git Service.
dmvolod opened a new pull request #26: Fix typo in print integration context
URL: https://github.com/apache/camel-k/pull/26
This is an automated message from the Apache Git Service.
To respond to the message, please log on Gi
nicolaferraro closed pull request #24: initial code for integration context
URL: https://github.com/apache/camel-k/pull/24
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull
nicolaferraro closed pull request #23: Add label to service
URL: https://github.com/apache/camel-k/pull/23
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a
lburgazzoli commented on a change in pull request #24: initial code for
integration context
URL: https://github.com/apache/camel-k/pull/24#discussion_r216677678
##
File path: pkg/client/cmd/context_edit.go
##
@@ -0,0 +1,101 @@
+/*
+Licensed to the Apache Software Foundatio
lburgazzoli commented on a change in pull request #24: initial code for
integration context
URL: https://github.com/apache/camel-k/pull/24#discussion_r216677379
##
File path: pkg/apis/camel/v1alpha1/types.go
##
@@ -61,3 +62,53 @@ const (
IntegrationPhaseRunning I
lburgazzoli closed pull request #25: Changed log message in Sample.java in
order to really rocks!
URL: https://github.com/apache/camel-k/pull/25
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As
dmvolod commented on a change in pull request #23: Add label to service
URL: https://github.com/apache/camel-k/pull/23#discussion_r216677017
##
File path: README.md
##
@@ -46,6 +46,12 @@ kamel install
This will configure the cluster with the Camel K custom resource defin
dmvolod commented on a change in pull request #23: Add label to service
URL: https://github.com/apache/camel-k/pull/23#discussion_r216676928
##
File path: deploy/operator-service.yaml
##
@@ -0,0 +1,19 @@
+apiVersion: v1
Review comment:
Yes, this is for metrics. It cre
valdar opened a new pull request #25: Changed log message in Sample.java in
order to really rocks!
URL: https://github.com/apache/camel-k/pull/25
This is an automated message from the Apache Git Service.
To respond to the me
nicolaferraro commented on a change in pull request #24: initial code for
integration context
URL: https://github.com/apache/camel-k/pull/24#discussion_r216661986
##
File path: pkg/stub/action/context/monitor.go
##
@@ -0,0 +1,46 @@
+/*
+Licensed to the Apache Software Foun
nicolaferraro commented on a change in pull request #24: initial code for
integration context
URL: https://github.com/apache/camel-k/pull/24#discussion_r216658126
##
File path: Gopkg.lock
##
@@ -2,230 +2,179 @@
[[projects]]
- digest = "1:5c3894b2aa4d6bead0ceeea6831b3
nicolaferraro commented on a change in pull request #24: initial code for
integration context
URL: https://github.com/apache/camel-k/pull/24#discussion_r216658402
##
File path: pkg/apis/camel/v1alpha1/types.go
##
@@ -36,6 +36,7 @@ type Integration struct {
metav1.O
nicolaferraro commented on a change in pull request #24: initial code for
integration context
URL: https://github.com/apache/camel-k/pull/24#discussion_r216658930
##
File path: pkg/apis/camel/v1alpha1/types.go
##
@@ -61,3 +62,53 @@ const (
IntegrationPhaseRunning
nicolaferraro commented on a change in pull request #24: initial code for
integration context
URL: https://github.com/apache/camel-k/pull/24#discussion_r216660873
##
File path: pkg/client/cmd/context_edit.go
##
@@ -0,0 +1,101 @@
+/*
+Licensed to the Apache Software Foundat
nicolaferraro commented on a change in pull request #23: Add label to service
URL: https://github.com/apache/camel-k/pull/23#discussion_r216657892
##
File path: deploy/resources.go
##
@@ -86,7 +86,6 @@ spec:
metadata:
labels:
name: camel-k-operator
-
nicolaferraro commented on a change in pull request #23: Add label to service
URL: https://github.com/apache/camel-k/pull/23#discussion_r216656331
##
File path: deploy/operator-service.yaml
##
@@ -0,0 +1,19 @@
+apiVersion: v1
Review comment:
I mean the service
--
nicolaferraro commented on a change in pull request #23: Add label to service
URL: https://github.com/apache/camel-k/pull/23#discussion_r216656035
##
File path: deploy/resources.go
##
@@ -86,7 +86,6 @@ spec:
metadata:
labels:
name: camel-k-operator
-
nicolaferraro commented on a change in pull request #23: Add label to service
URL: https://github.com/apache/camel-k/pull/23#discussion_r216646302
##
File path: README.md
##
@@ -46,6 +46,12 @@ kamel install
This will configure the cluster with the Camel K custom resource
nicolaferraro commented on a change in pull request #23: Add label to service
URL: https://github.com/apache/camel-k/pull/23#discussion_r216646603
##
File path: deploy/operator-service.yaml
##
@@ -0,0 +1,19 @@
+apiVersion: v1
Review comment:
Ok, is this required for t
dmvolod opened a new pull request #23: Add label to service
URL: https://github.com/apache/camel-k/pull/23
Missing to add label to service. This requires to separate service creation
in single file operator-service.yaml.
This
lburgazzoli closed pull request #22: CAMEL-12789: complete install command
URL: https://github.com/apache/camel-k/pull/22
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull r
nicolaferraro opened a new pull request #22: CAMEL-12789: complete install
command
URL: https://github.com/apache/camel-k/pull/22
This is an automated message from the Apache Git Service.
To respond to the message, please lo
nicolaferraro closed pull request #21: Add labels to all resources
URL: https://github.com/apache/camel-k/pull/21
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (
nicolaferraro commented on issue #21: Add labels to all resources
URL: https://github.com/apache/camel-k/pull/21#issuecomment-420217342
Yes, sounds good!
This is an automated message from the Apache Git Service.
To respond to
dmvolod opened a new pull request #21: Add labels to all resources
URL: https://github.com/apache/camel-k/pull/21
Add labels to resources. It will be useful if we will add an 'uninstall'
option in the future and remove or update can easy with one command, i.e.
oc delete
all,pvc,conf
lburgazzoli closed pull request #20: CAMEL-12798: Add getting started guide
URL: https://github.com/apache/camel-k/pull/20
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull
nicolaferraro opened a new pull request #20: CAMEL-12798: Add getting started
guide
URL: https://github.com/apache/camel-k/pull/20
This is an automated message from the Apache Git Service.
To respond to the message, please l
nicolaferraro closed pull request #19: runtime: add support for groovy
URL: https://github.com/apache/camel-k/pull/19
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull reque
oscerd closed pull request #18: Installation and run works
URL: https://github.com/apache/camel-k/pull/18
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a f
80 matches
Mail list logo
