camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gilfernandes <>
Subject [GitHub] camel pull request #1278: New Firebase Camel Component
Date Fri, 18 Nov 2016 16:29:08 GMT
GitHub user gilfernandes opened a pull request:

    New Firebase Camel Component

    This component should allow to use Firebase (see [](
) from Camel. It contains an end point with a Producer and a Consumer. The producer can create
and update values in Firebase. The consumer listens to child events and can consume add, change,
remove, move and cancel operations.
    You will find some integration unit tests in this first commit. But these tests will need
to have a JSON file ('firebase-admin-connection.json') with the Firebase keys so that the
tests can run. For security reasons I have removed these. Not quite sure how to solve that.
    I am a newbie on this project, so it might well be that I am not complying to your standards.
Please guide me where needed.

You can merge this pull request into a Git repository by running:

    $ git pull master

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1278
commit 013e19f4c0d8194419ff66f0e36c7fd2cc146bb2
Author: gilfernandes <>
Date:   2016-11-18T15:57:33Z

    Added first version of the Camel Firebase component.

commit 410d771821b1daf7e3de3b02671980e7db0b93f0
Author: gilfernandes <>
Date:   2016-11-18T16:10:46Z

    Added first version of the Camel Firebase component.

commit 9fedbbb4eae13efca03f6dfaf60cf1ec2b27be79
Author: gilfernandes <>
Date:   2016-11-18T16:14:15Z

    Committed renamed firebase connection file.

commit c86c7423b8a1cee94bbc846ef24b56e09023e35b
Author: gilfernandes <>
Date:   2016-11-18T16:19:44Z

    Renamed the Firebase admin configuration file.

commit 95800318c1224a92b9657da5c2f925c0c704245f
Author: gilfernandes <>
Date:   2016-11-18T16:21:51Z

    Removed sensitive data.


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message