diff options
author | Scott Dodson <sdodson@redhat.com> | 2017-10-23 21:25:25 -0400 |
---|---|---|
committer | Scott Dodson <sdodson@redhat.com> | 2017-10-23 21:25:25 -0400 |
commit | f7728996fbe2ad109fc8290682493038bc43f66c (patch) | |
tree | bada0b119b081def984a3945d9c0c9175d27f384 /roles/openshift_examples/files/examples/v3.7/xpaas-templates/spring-boot-camel-amq-template.json | |
parent | d3ae358d8eda7d74a158d9ff7de3a23fca4e8b51 (diff) | |
download | openshift-f7728996fbe2ad109fc8290682493038bc43f66c.tar.gz openshift-f7728996fbe2ad109fc8290682493038bc43f66c.tar.bz2 openshift-f7728996fbe2ad109fc8290682493038bc43f66c.tar.xz openshift-f7728996fbe2ad109fc8290682493038bc43f66c.zip |
Sync latest imagestreams and templates
Diffstat (limited to 'roles/openshift_examples/files/examples/v3.7/xpaas-templates/spring-boot-camel-amq-template.json')
-rw-r--r-- | roles/openshift_examples/files/examples/v3.7/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.7/xpaas-templates/spring-boot-camel-amq-template.json b/roles/openshift_examples/files/examples/v3.7/xpaas-templates/spring-boot-camel-amq-template.json index 8b3cd6ed0..2c1a73a29 100644 --- a/roles/openshift_examples/files/examples/v3.7/xpaas-templates/spring-boot-camel-amq-template.json +++ b/roles/openshift_examples/files/examples/v3.7/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.", + "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", "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-000055", + "value": "spring-boot-camel-amq-1.0.0.redhat-000064", "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-000055", + "value": "1.0.0.redhat-000064", "description": "The application version." }, { |