There is an ongoing issue of gfsh>start pulse where the gorouters block all but 8080 traffic. The workaround was to take the locator[0] ip and place in the url like http://<locator[0]>:8080/pulse. This seems to work.

update the jar file name in manifest.yml

Update pom to include the Spring Test support for Gemfire.
Add test module that demonstrates the mocking of region (see PizzaOrderTest).

Feedback from the workshop that it wasn't straight forward to support the local profile. @nchandrappa has already done some work and committed which included:

• DBLocalConfig.java - a local config that assigns the @Profile("local")

Now we need to setup the properties file to support the local and cloud profiles. Right now you uncomment the profile and set it to local and uncomment the hsqldb dependent in the pom file. To complete:

• Add the local profile in the setup documentation lab.
• Add the local profile into the properties file so that we don't need to comment/uncomment the property
• (I think) just leave the hsqldb dependency uncommented.
• Update 01_environment_setup.md to accomodate the local env setup.

It was confusing to the users when the keystore information prompts pop up during the first connection to gfsh. We need to explain local vs remote and what it means to have self signed certs.