platform-api 3.0.0 → 3.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ee0c328970505aab87e732a3030917e1a39a13ace925bee458a64e7c46e2b4a2
-  data.tar.gz: c6c5e31213b1cb83e778644602090eafb62fedd13f2e25705c65a9667b65f3ba
+  metadata.gz: 1383efaefd3565fdcbee73f42d9dbb2149d83d57a267a5370339c747b48bf117
+  data.tar.gz: 7ce7b087648836e4c4d45168f58aaa84c775ae23a94544833f483aa1288b7370
 SHA512:
-  metadata.gz: dc9b94a51665c7baa26970c7a29fb8aa73611150ace42da706c0cfff817761c92d5c6cceb283a6fc7bd0182bbf6eae6624008d07befd48ba1cd908640e1a57d9
-  data.tar.gz: 382c4beea5afac407fc0d34b88d9e376390a015fcf023bfe7bb422111785481e4752f73a810a353c37178f8d36925e97d1dc149273d07781524c42f52c842147
+  metadata.gz: 421275c5af1466282481910d4b83b4e92ec75d1e4888b652db0de76dd8aec0f26ffaf7c12176adafe4cf03e0a4e6b748fad9975efd0432f136bbbc77301d8f3e
+  data.tar.gz: bff00809ee73304d3b144aef3b966333c3ee57c118b32f200a26cb8f0c6504de72f99259d470c13cd55265a8db7f82ace091de203edb103d68deace172e6ab5d

data/CHANGELOG.md

@@ -1,5 +1,25 @@
 ## Master (unreleased)
 
+## 3.5.0
+
+- Pull latest JSON Schema and regenerated API.
+
+## 3.4.0
+
+- Pull latest JSON Schema and regenerated API.
+
+## 3.3.0
+
+- Pull latest JSON Schema and regenerated API.
+
+## 3.2.0
+
+- Pull latest JSON Schema and regenerated API.
+
+## 3.1.0
+
+- Pull latest JSON Schema and regenerated API.
+
 ## 3.0.0
 
 - Rate throttling is on by default. (https://github.com/heroku/platform-api/pull/104)

data/CODEOWNERS

@@ -0,0 +1,2 @@
+# Comment line immediately above ownership line is reserved for related gus information. Please be careful while editing.
+#ECCN:Open Source

data/README.md

@@ -159,7 +159,7 @@ heroku.app.info('floating-retreat-4255')
 Let's add a Heroku PostgreSQL database to our app now:
 
 ```ruby
-heroku.addon.create('floating-retreat-4255', {'plan' => 'heroku-postgresql:dev'})
+heroku.addon.create('floating-retreat-4255', {'plan' => 'heroku-postgresql:hobby-dev'})
 => {"config_vars"=>["HEROKU_POSTGRESQL_COBALT_URL"],
     "created_at"=>"2014-03-13T00:28:55Z",
     "id"=>"79a0c826-06be-4dcd-8bb5-f2c1b1bc2beb",
@@ -236,7 +236,7 @@ heroku.formation.list('floating-retreat-4255')
      "id"=>"f682b260-8089-4e18-b792-688cc02bf923",
      "type"=>"web",
      "quantity"=>1,
-     "size"=>"1X",
+     "size"=>"Standard-1X",
      "updated_at"=>"2014-03-13T04:13:37Z"}]
 ```
 
@@ -246,13 +246,13 @@ Let's change `web` process to run on a 2X dyno:
 heroku.formation.batch_update('floating-retreat-4255',
                               {"updates" => [{"process" => "web",
                                               "quantity" => 1,
-                                              "size" => "2X"}]})
+                                              "size" => "Standard-2X"}]})
 => [{"command"=>"coffee index.coffee",
      "created_at"=>"2014-03-13T04:13:37Z",
      "id"=>"f682b260-8089-4e18-b792-688cc02bf923",
      "type"=>"web",
      "quantity"=>1,
-     "size"=>"2X",
+     "size"=>"Standard-2X",
      "updated_at"=>"2014-03-13T04:22:15Z"}]
 ```
 
@@ -261,13 +261,13 @@ command.  We can use the singular update action to modify a single formation
 type:
 
 ```ruby
-heroku.formation.update('floating-retreat-4255', 'web', {"size" => "1X"})
+heroku.formation.update('floating-retreat-4255', 'web', {"size" => "Standard-1X"})
 => {"command"=>"coffee index.coffee",
     "created_at"=>"2014-03-13T04:13:37Z",
     "id"=>"f682b260-8089-4e18-b792-688cc02bf923",
     "type"=>"web",
     "quantity"=>1,
-    "size"=>"1X",
+    "size"=>"Standard-1X",
     "updated_at"=>"2014-03-13T04:24:46Z"}
 ```