jrussett

#############
# Resources #
#############
# Active Health Monitors
resource "nsxt_lb_http_monitor" "lb_web_monitor" {
  description           = "The Active Health Monitor (healthcheck) for Web (HTTP(S)) traffic."
  display_name          = "${var.nsxt_lb_web_monitor_name}"
  monitor_port          = 8080
  request_method        = "GET"
  request_url           = "/health"

wolfoo2931

#!/bin/bash

cert_names=`credhub curl -p /api/v1/certificates | jq '.certificates | .[].name'`

for cert in $cert_names; do
  cert_json=`credhub get -n $cert --output-json`
  echo $cert_json | jq '.value | .ca' -r > /tmp/tmpca
  echo $cert_json | jq '.value | .certificate' -r > /tmp/tmpcert

  if [[ $(< /tmp/tmpca) != "null" ]]; then

Gerg

#!/usr/bin/env ruby

require 'pp'

SCOPE_USERS = {
 admin: 'admin',
 admin_read_only: 'admin_read_only',
 global_auditor: 'global_auditor',
}

Amit-PivotalLabs

BOSH Links: Why and How

Audience: anyone in the BOSH ecosystem, whether you work on something open-source or proprietary

"BOSH Links" is a feature which simplifies how data is shared between BOSH-deployed jobs that need to collaborate with one another (e.g. a web server and its backing database). Like many BOSH things, the whole "BOSH Links" thing can seem counter-intuitive at first, and it may not be clear why things are the way they are. This note hopes to show some of the powerful benefits of BOSH Links, and provide examples and explanations that make things more intuitive.

1. Why?
2. BASIC: A simple problem statement
3. BASIC: Putting the puzzle pieces together
4. ADVANCED: But what about...