platform-api 3.3.0 → 3.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 775b3ebd7968c6a1b1020cbbd50d99da0ad114e4029466bb84c18866032806fe
-  data.tar.gz: 82c37b81372786f9f17c34fe34e4697b9a69473988f031487d89bd15867687de
+  metadata.gz: 1383efaefd3565fdcbee73f42d9dbb2149d83d57a267a5370339c747b48bf117
+  data.tar.gz: 7ce7b087648836e4c4d45168f58aaa84c775ae23a94544833f483aa1288b7370
 SHA512:
-  metadata.gz: f4cb07e01e08984f9ecf719a3e224b4aba9bb98a32a1958a8b0601a2a9f57bf5e6cb17dfc85f78f7cbb43faff1b4781fb72d01ba376a36fd7996577bb70f71e7
-  data.tar.gz: 99ea044167c91df670b2b7eea460a0318b7bfb90be0d5e128ead80c35f3f39add880ec69394544a5465f25ddf3ceb373659c7e5668a31dbbe096d37ceae5d9b6
+  metadata.gz: 421275c5af1466282481910d4b83b4e92ec75d1e4888b652db0de76dd8aec0f26ffaf7c12176adafe4cf03e0a4e6b748fad9975efd0432f136bbbc77301d8f3e
+  data.tar.gz: bff00809ee73304d3b144aef3b966333c3ee57c118b32f200a26cb8f0c6504de72f99259d470c13cd55265a8db7f82ace091de203edb103d68deace172e6ab5d

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 ## 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.

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"}
 ```