Just point the monitoring CNAME to the fqdn for now

rubygems · Jul 10, 2014 · f55b253 · f55b253
1 parent b27b9bc
commit f55b253
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/Berksfile.lock b/Berksfile.lock
@@ -249,7 +249,7 @@ GRAPH
     collectd (>= 0.0.0)
     collectd-librato (>= 0.0.0)
     collectd_plugins (>= 0.0.0)
-  rubygems-monitoring (0.0.9)
+  rubygems-monitoring (0.0.10)
     chef-vault (>= 0.0.0)
     dwradcliffe-dnsimple (>= 0.0.0)
     nginx (>= 0.0.0)

diff --git a/cookbooks/rubygems-monitoring/metadata.rb b/cookbooks/rubygems-monitoring/metadata.rb
@@ -1,7 +1,7 @@
 name 'rubygems-monitoring'
 maintainer 'RubyGems.org ops team'
 
-version '0.0.9'
+version '0.0.10'
 
 depends 'chef-vault'
 depends 'dwradcliffe-dnsimple'

diff --git a/cookbooks/rubygems-monitoring/recipes/default.rb b/cookbooks/rubygems-monitoring/recipes/default.rb
@@ -11,7 +11,7 @@
 
 dwradcliffe_dnsimple_record "create CNAME point monitoring.rubygems.org to #{node.name}" do
   name     'monitoring.rubygems.org'
-  content  node['cloud_v2']['public_hostname']
+  content  node['fqdn']
   type     'CNAME'
   domain   'rubygems.org'
   username dnsimple_credentials['username']