diff options
author | Scott Dodson <sdodson@redhat.com> | 2018-02-08 20:02:21 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2018-02-08 20:02:21 -0500 |
commit | 7add856d112f60f06495906a2b1aebc6ef99b623 (patch) | |
tree | f3f3d7e3789794e2842986e6b8f1a90a86ee8df4 /roles/openshift_examples/files/examples/v3.8/xpaas-templates/spring-boot-camel-amq-template.json | |
parent | 3489d4f75fd2773f5fa5a684b82bf8ca44f1fa02 (diff) | |
parent | f52ac0d10b4c5f1219a4af9fa659659d5aff5012 (diff) | |
download | openshift-7add856d112f60f06495906a2b1aebc6ef99b623.tar.gz openshift-7add856d112f60f06495906a2b1aebc6ef99b623.tar.bz2 openshift-7add856d112f60f06495906a2b1aebc6ef99b623.tar.xz openshift-7add856d112f60f06495906a2b1aebc6ef99b623.zip |
Merge pull request #7014 from sdodson/xpaas-148
Update xPaaS content to v1.4.8
Diffstat (limited to 'roles/openshift_examples/files/examples/v3.8/xpaas-templates/spring-boot-camel-amq-template.json')
-rw-r--r-- | roles/openshift_examples/files/examples/v3.8/xpaas-templates/spring-boot-camel-amq-template.json | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/roles/openshift_examples/files/examples/v3.8/xpaas-templates/spring-boot-camel-amq-template.json b/roles/openshift_examples/files/examples/v3.8/xpaas-templates/spring-boot-camel-amq-template.json index 2c1a73a29..89f10f955 100644 --- a/roles/openshift_examples/files/examples/v3.8/xpaas-templates/spring-boot-camel-amq-template.json +++ b/roles/openshift_examples/files/examples/v3.8/xpaas-templates/spring-boot-camel-amq-template.json @@ -3,7 +3,7 @@ "kind": "Template", "metadata": { "annotations": { - "description": "Spring Boot, Camel and ActiveMQ QuickStart. This quickstart demonstrates how to connect a Spring-Boot application to an ActiveMQ broker and use JMS messaging between two Camel routes using OpenShift. In this example we will use two containers, one container to run as a ActiveMQ broker, and another as a client to the broker, where the Camel routes are running. This quickstart requires the ActiveMQ broker has been deployed and running first, one simple way to run a A-MQ service is following the documentation of the A-MQ xPaaS image for OpenShift related to the amq62-basic template", + "description": "Spring Boot, Camel and ActiveMQ QuickStart. This quickstart demonstrates how to connect a Spring-Boot application to an ActiveMQ broker and use JMS messaging between two Camel routes using OpenShift. In this example we will use two containers, one container to run as a ActiveMQ broker, and another as a client to the broker, where the Camel routes are running. This quickstart requires the ActiveMQ broker has been deployed and running first, one simple way to run a A-MQ service is following the documentation of the A-MQ xPaaS image for OpenShift related to the amq63-basic template", "tags": "quickstart,java,springboot,fis", "iconClass": "icon-jboss", "version": "2.0" @@ -31,7 +31,7 @@ { "name": "GIT_REF", "displayName": "Git Reference", - "value": "spring-boot-camel-amq-1.0.0.redhat-000064", + "value": "spring-boot-camel-amq-1.0.0.redhat-000067", "description": "Set this to a branch name, tag or other ref of your repository if you are not using the default branch." }, { @@ -60,7 +60,7 @@ { "name": "APP_VERSION", "displayName": "Application Version", - "value": "1.0.0.redhat-000064", + "value": "1.0.0.redhat-000067", "description": "The application version." }, { |