sivel

vars_secret_funky_json: !vault |
  $ANSIBLE_VAULT;1.2;AES256;alan_host
  35356666616633303337313766346562613961313262333530663432393965303736653334306433
  6239666265343936343462653836386162343234353961330a306665396665353364613863316362
  66646663313737393763383565333237316663666339623063646666646261643338616261633330
  3634313634666264620a383632386661653330326435633861333031643334643237366430313733
  3733

{
    "vars_secret_funky_json": {

Faheetah

node {
    echo 'Results included as an inline comment exactly how they are returned as of Jenkins 2.121, with $BUILD_NUMBER = 1'
    echo 'No quotes, pipeline command in single quotes'
    sh 'echo $BUILD_NUMBER' // 1
    echo 'Double quotes are silently dropped'
    sh 'echo "$BUILD_NUMBER"' // 1
    echo 'Even escaped with a single backslash they are dropped'
    sh 'echo \"$BUILD_NUMBER\"' // 1
    echo 'Using two backslashes, the quotes are preserved'
    sh 'echo \\"$BUILD_NUMBER\\"' // "1"

pogzie

## Caveats
1. The CN on the `Generate a Key and CSR for Riak Node` The CN section of the subject must match the FQDN of the server, or the certificate verification will fail. A wildcard (or SANs) may be used to avoid generating different certificates for different nodes (Particularly helpful when behind a load balancer). 
    1. If you are using your local machine to check/test add to /etc/hosts the node name 
2. Note that a Mac machine uses an old version of OpenSSL (could be checked using `openssl version`) it will have problems with the generated certificates
    1. Generated working certificates using Ubuntu with OpenSSL version OpenSSL 1.0.1f 6 Jan 2014.
	2. In Mac, upgrading SSL and changing the symlink to point to the homebrew version works fine. Homebrew installed OpenSSL 1.0.2e 3 Dec 2015 works. 
3. When testing with a browser, you WILL need to confirm the security exception. 
4. Make sure that you disable the listener.http.internal and enable `listener.https.internal` on the Riak config.
5. Please e