diff --git a/multi/multi__encryption_and_decryption.html b/multi/multi__encryption_and_decryption.html index fed3d23..a57f75a 100644 --- a/multi/multi__encryption_and_decryption.html +++ b/multi/multi__encryption_and_decryption.html @@ -1,6 +1,6 @@ - 4. Encryption and Decryption
4. Encryption and Decryption
Prev   

4. Encryption and Decryption

The Spring Cloud CLI comes with an "encrypt" and a "decrypt" + 4. Encryption and Decryption

4. Encryption and Decryption
Prev   

4. Encryption and Decryption

The Spring Cloud CLI comes with an "encrypt" and a "decrypt" command. Both accept arguments in the same form with a key specified as a mandatory "--key", e.g.

$ spring encrypt mysecret --key foo
 682bc583f4641835fa2db009355293665d2647dade3375c0ee201de2a49f7bda
diff --git a/multi/multi__installation.html b/multi/multi__installation.html
index 43cb885..7e5c2c8 100644
--- a/multi/multi__installation.html
+++ b/multi/multi__installation.html
@@ -1,12 +1,12 @@
 
       
-   1. Installation
1. Installation
Prev   Next
1. Installation
To install, make
+   1. Installation
1. Installation
Prev   Next
1. Installation
To install, make
 sure you have
 Spring Boot CLI
 (2.0.0 or better):
$ spring version
-Spring CLI v2.0.0.M6
E.g. for SDKMan users
$ sdk install springboot 2.0.0.M6
-$ sdk use springboot 2.0.0.M6
and install the Spring Cloud plugin
$ mvn install
-$ spring install org.springframework.cloud:spring-cloud-cli:2.0.1.BUILD-SNAPSHOT
[Important]Important
Prerequisites: to use the encryption and decryption features
+Spring CLI v2.1.0.M4
E.g. for SDKMan users
$ sdk install springboot 2.1.0.M4
+$ sdk use springboot 2.1.0.M4
and install the Spring Cloud plugin
$ mvn install
+$ spring install org.springframework.cloud:spring-cloud-cli:2.1.0.BUILD-SNAPSHOT
[Important]Important
Prerequisites: to use the encryption and decryption features
 you need the full-strength JCE installed in your JVM (it’s not there by default).
 You can download the "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files"
 from Oracle, and follow instructions for installation (essentially replace the 2 policy files
diff --git a/multi/multi__running_spring_cloud_services_in_development.html b/multi/multi__running_spring_cloud_services_in_development.html
index 74052e7..bef7209 100644
--- a/multi/multi__running_spring_cloud_services_in_development.html
+++ b/multi/multi__running_spring_cloud_services_in_development.html
@@ -1,10 +1,10 @@
 
       
-   2. Running Spring Cloud Services in Development
2. Running Spring Cloud Services in Development
Prev   Next
2. Running Spring Cloud Services in Development
The Launcher CLI can be used to run common services like Eureka,
+   2. Running Spring Cloud Services in Development
2. Running Spring Cloud Services in Development
Prev   Next
2. Running Spring Cloud Services in Development
The Launcher CLI can be used to run common services like Eureka,
 Config Server etc. from the command line. To list the available
 services you can do spring cloud --list, and to launch a default set
 of services just spring cloud. To choose the services to deploy,
-just list them on the command line, e.g.
$ spring cloud eureka configserver h2 kafka stubrunner zipkin
Summary of supported deployables:
ServiceNameAddressDescription
eureka
Eureka Server
http://localhost:8761
Eureka server for service registration and discovery. All the other services show up in its catalog by default.
configserver
Config Server
http://localhost:8888
Spring Cloud Config Server running in the "native" profile and serving configuration from the local directory ./launcher
h2
H2 Database
http://localhost:9095 (console), jdbc:h2:tcp://localhost:9096/{data}
Relation database service. Use a file path for {data} (e.g. ./target/test) when you connect. Remember that you can add ;MODE=MYSQL or ;MODE=POSTGRESQL to connect with compatibility to other server types.
kafka
Kafka Broker
http://localhost:9091 (actuator endpoints), localhost:9092
 
hystrixdashboard
Hystrix Dashboard
http://localhost:7979
Any Spring Cloud app that declares Hystrix circuit breakers publishes metrics on /hystrix.stream. Type that address into the dashboard to visualize all the metrics,
dataflow
Dataflow Server
http://localhost:9393
Spring Cloud Dataflow server with UI at /admin-ui. Connect the Dataflow shell to target at root path.
zipkin
Zipkin Server
http://localhost:9411
Zipkin Server with UI for visualizing traces. Stores span data in memory and accepts them via HTTP POST of JSON data.
stubrunner
Stub Runner Boot
http://localhost:8750
Downloads WireMock stubs, starts WireMock and feeds the started servers with stored stubs. Pass stubrunner.ids to pass stub coordinates and then go to http://localhost:8750/stubs.
Each of these apps can be configured using a local YAML file with the same name (in the current
+just list them on the command line, e.g.
$ spring cloud eureka configserver h2 kafka stubrunner zipkin
Summary of supported deployables:
ServiceNameAddressDescription
eureka
Eureka Server
http://localhost:8761
Eureka server for service registration and discovery. All the other services show up in its catalog by default.
configserver
Config Server
http://localhost:8888
Spring Cloud Config Server running in the "native" profile and serving configuration from the local directory ./launcher
h2
H2 Database
http://localhost:9095 (console), jdbc:h2:tcp://localhost:9096/{data}
Relation database service. Use a file path for {data} (e.g. ./target/test) when you connect. Remember that you can add ;MODE=MYSQL or ;MODE=POSTGRESQL to connect with compatibility to other server types.
kafka
Kafka Broker
http://localhost:9091 (actuator endpoints), localhost:9092
 
hystrixdashboard
Hystrix Dashboard
http://localhost:7979
Any Spring Cloud app that declares Hystrix circuit breakers publishes metrics on /hystrix.stream. Type that address into the dashboard to visualize all the metrics,
dataflow
Dataflow Server
http://localhost:9393
Spring Cloud Dataflow server with UI at /admin-ui. Connect the Dataflow shell to target at root path.
zipkin
Zipkin Server
http://localhost:9411
Zipkin Server with UI for visualizing traces. Stores span data in memory and accepts them via HTTP POST of JSON data.
stubrunner
Stub Runner Boot
http://localhost:8750
Downloads WireMock stubs, starts WireMock and feeds the started servers with stored stubs. Pass stubrunner.ids to pass stub coordinates and then go to http://localhost:8750/stubs.
Each of these apps can be configured using a local YAML file with the same name (in the current
 working directory or a subdirectory called "config" or in ~/.spring-cloud). E.g. in configserver.yml you might want to
 do something like this to locate a local git repository for the backend:
configserver.yml. 
 
spring:
diff --git a/multi/multi__writing_groovy_scripts_and_running_applications.html b/multi/multi__writing_groovy_scripts_and_running_applications.html
index b2e02cd..1052519 100644
--- a/multi/multi__writing_groovy_scripts_and_running_applications.html
+++ b/multi/multi__writing_groovy_scripts_and_running_applications.html
@@ -1,6 +1,6 @@
 
       
-   3. Writing Groovy Scripts and Running Applications
3. Writing Groovy Scripts and Running Applications
Prev   Next
3. Writing Groovy Scripts and Running Applications
Spring Cloud CLI has support for most of the Spring Cloud declarative
+   3. Writing Groovy Scripts and Running Applications
3. Writing Groovy Scripts and Running Applications
Prev   Next
3. Writing Groovy Scripts and Running Applications
Spring Cloud CLI has support for most of the Spring Cloud declarative
 features, such as the @Enable* class of annotations. For example,
 here is a fully functional Eureka server
app.groovy. 
 
@EnableEurekaServer
diff --git a/multi/multi_pr01.html b/multi/multi_pr01.html
index 2a88230..d669cd7 100644
--- a/multi/multi_pr01.html
+++ b/multi/multi_pr01.html
@@ -1,6 +1,6 @@
 
       
-   
Prev   Next
Spring Boot CLI provides Spring
+   
Prev   Next
Spring Boot CLI provides Spring
 Boot command line features for Spring
 Cloud. You can write Groovy scripts to run Spring Cloud component
 applications (e.g. @EnableEurekaServer). You can also easily do
diff --git a/multi/multi_spring-cloud-cli.html b/multi/multi_spring-cloud-cli.html
index fd7a6f2..01959df 100644
--- a/multi/multi_spring-cloud-cli.html
+++ b/multi/multi_spring-cloud-cli.html
@@ -1,3 +1,3 @@
 
       
-   Spring Boot Cloud CLI
Spring Boot Cloud CLI
   Next
Spring Boot Cloud CLI
Table of Contents
1. Installation
2. Running Spring Cloud Services in Development
2.1. Adding Additional Applications
3. Writing Groovy Scripts and Running Applications
4. Encryption and Decryption
   Next
   

\ No newline at end of file
+   Spring Boot Cloud CLI
Spring Boot Cloud CLI
   Next
Spring Boot Cloud CLI
Table of Contents
1. Installation
2. Running Spring Cloud Services in Development
2.1. Adding Additional Applications
3. Writing Groovy Scripts and Running Applications
4. Encryption and Decryption
   Next
   

\ No newline at end of file
diff --git a/single/spring-cloud-cli.html b/single/spring-cloud-cli.html
index 16edd5a..077cb1b 100644
--- a/single/spring-cloud-cli.html
+++ b/single/spring-cloud-cli.html
@@ -1,6 +1,6 @@
 
       
-   Spring Boot Cloud CLI
Spring Boot Cloud CLI
Table of Contents
1. Installation
2. Running Spring Cloud Services in Development
2.1. Adding Additional Applications
3. Writing Groovy Scripts and Running Applications
4. Encryption and Decryption
Spring Boot CLI provides Spring
+   Spring Boot Cloud CLI
Spring Boot Cloud CLI
Table of Contents
1. Installation
2. Running Spring Cloud Services in Development
2.1. Adding Additional Applications
3. Writing Groovy Scripts and Running Applications
4. Encryption and Decryption
Spring Boot CLI provides Spring
 Boot command line features for Spring
 Cloud. You can write Groovy scripts to run Spring Cloud component
 applications (e.g. @EnableEurekaServer). You can also easily do
@@ -12,9 +12,9 @@ development time).
Spring Boot CLI
 (2.0.0 or better):
$ spring version
-Spring CLI v2.0.0.M6
E.g. for SDKMan users
$ sdk install springboot 2.0.0.M6
-$ sdk use springboot 2.0.0.M6
and install the Spring Cloud plugin
$ mvn install
-$ spring install org.springframework.cloud:spring-cloud-cli:2.0.1.BUILD-SNAPSHOT
[Important]Important
Prerequisites: to use the encryption and decryption features
+Spring CLI v2.1.0.M4
E.g. for SDKMan users
$ sdk install springboot 2.1.0.M4
+$ sdk use springboot 2.1.0.M4
and install the Spring Cloud plugin
$ mvn install
+$ spring install org.springframework.cloud:spring-cloud-cli:2.1.0.BUILD-SNAPSHOT
spring cloud --list, and to launch a default set
 of services just spring cloud. To choose the services to deploy,
-just list them on the command line, e.g.
$ spring cloud eureka configserver h2 kafka stubrunner zipkin
Summary of supported deployables:
[Important]Important
Prerequisites: to use the encryption and decryption features
 you need the full-strength JCE installed in your JVM (it’s not there by default).
 You can download the "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files"
 from Oracle, and follow instructions for installation (essentially replace the 2 policy files
@@ -22,7 +22,7 @@ in the JRE lib/security directory with the ones that you downloaded).
ServiceNameAddressDescription
eureka
Eureka Server
http://localhost:8761
Eureka server for service registration and discovery. All the other services show up in its catalog by default.
configserver
Config Server
http://localhost:8888
Spring Cloud Config Server running in the "native" profile and serving configuration from the local directory ./launcher
h2
H2 Database
http://localhost:9095 (console), jdbc:h2:tcp://localhost:9096/{data}
Relation database service. Use a file path for {data} (e.g. ./target/test) when you connect. Remember that you can add ;MODE=MYSQL or ;MODE=POSTGRESQL to connect with compatibility to other server types.
kafka
Kafka Broker
http://localhost:9091 (actuator endpoints), localhost:9092
 
hystrixdashboard
Hystrix Dashboard
http://localhost:7979
Any Spring Cloud app that declares Hystrix circuit breakers publishes metrics on /hystrix.stream. Type that address into the dashboard to visualize all the metrics,
dataflow
Dataflow Server
http://localhost:9393
Spring Cloud Dataflow server with UI at /admin-ui. Connect the Dataflow shell to target at root path.
zipkin
Zipkin Server
http://localhost:9411
Zipkin Server with UI for visualizing traces. Stores span data in memory and accepts them via HTTP POST of JSON data.
stubrunner
Stub Runner Boot
http://localhost:8750
Downloads WireMock stubs, starts WireMock and feeds the started servers with stored stubs. Pass stubrunner.ids to pass stub coordinates and then go to http://localhost:8750/stubs.
Each of these apps can be configured using a local YAML file with the same name (in the current
+just list them on the command line, e.g.
$ spring cloud eureka configserver h2 kafka stubrunner zipkin
Summary of supported deployables:
ServiceNameAddressDescription
eureka
Eureka Server
http://localhost:8761
Eureka server for service registration and discovery. All the other services show up in its catalog by default.
configserver
Config Server
http://localhost:8888
Spring Cloud Config Server running in the "native" profile and serving configuration from the local directory ./launcher
h2
H2 Database
http://localhost:9095 (console), jdbc:h2:tcp://localhost:9096/{data}
Relation database service. Use a file path for {data} (e.g. ./target/test) when you connect. Remember that you can add ;MODE=MYSQL or ;MODE=POSTGRESQL to connect with compatibility to other server types.
kafka
Kafka Broker
http://localhost:9091 (actuator endpoints), localhost:9092
 
hystrixdashboard
Hystrix Dashboard
http://localhost:7979
Any Spring Cloud app that declares Hystrix circuit breakers publishes metrics on /hystrix.stream. Type that address into the dashboard to visualize all the metrics,
dataflow
Dataflow Server
http://localhost:9393
Spring Cloud Dataflow server with UI at /admin-ui. Connect the Dataflow shell to target at root path.
zipkin
Zipkin Server
http://localhost:9411
Zipkin Server with UI for visualizing traces. Stores span data in memory and accepts them via HTTP POST of JSON data.
stubrunner
Stub Runner Boot
http://localhost:8750
Downloads WireMock stubs, starts WireMock and feeds the started servers with stored stubs. Pass stubrunner.ids to pass stub coordinates and then go to http://localhost:8750/stubs.
Each of these apps can be configured using a local YAML file with the same name (in the current
 working directory or a subdirectory called "config" or in ~/.spring-cloud). E.g. in configserver.yml you might want to
 do something like this to locate a local git repository for the backend:
configserver.yml. 
 
spring:
diff --git a/spring-cloud-cli.html b/spring-cloud-cli.html
index af8ab68..75dfb59 100644
--- a/spring-cloud-cli.html
+++ b/spring-cloud-cli.html
@@ -4,7 +4,7 @@
 
 
 
-
+
 spring-cloud-cli