heroku拿到这个配置文件后。才干知道服务的地址，资源接口。

这份配置，能够通过kensa来生成。有两个相关的命令，kensa init、kensa create。两者都能生成前文所述的配置文件--addon-manifest.json。不同之处在于，后者还能生成一个空的项目模版。

{"id": "errorbucket","api": {"config_vars": ["ERRORBUCKET_URL"],"password": "GqAGAmdrnkDFcvR9","sso_salt": "7CwqmJLEjv8YZTXK","regions": ["us","eu"],"requires": ["log_input"],"production": {"base_url": "https://errorbucket.com/heroku/resources","sso_url": "https://errorbucket.com/sso/login"},"test": {"base_url": "http://localhost:4567/heroku/resources","sso_url": "http://localhost:4567/sso/login"}}
}

仅仅同意这里指定的区域訪问服务。主要考虑到对时延高要求的服务，对地域要求较高。假设没办法给全部地区的用户都提供高质量服务，那就限制一下吧。

资源的增删改，都相应为同一个url。如https://username:password@api.youraddon.com/heroku/resources。请求类型为Post表示创建，DELETE表示删除（需带上id，如https://username:password@api.youraddon.com/heroku/resources/:id），PUT表示改动（带上id）

Request: POST https://username:password@api.youraddon.com/heroku/resources
Request Body: {"heroku_id": "app123@heroku.com","plan": "basic","region": "amazon-web-services::us-east-1","callback_url": "https://api.heroku.com/vendor/apps/app123%40heroku.com","log_input_url": "https://token:t.01234567-89ab-cdef-0123-456789abcdef@1.us.logplex.io/logs","options": {}
}
Response Body: {"id": "your-internal-unique-id","config": {"MYADDON_URL": "http://myaddon.com/52e82f5d73"},"message": "your message here"
}

Request: PUT https://username:password@api.youraddon.com/heroku/resources/:id
Request Body: {"heroku_id": "app123@heroku.com", "plan": "premium"}
Response Body: {"config": { ... }, "message": "your message here"}

Request: DELETE https://username:password@api.youraddon.com/heroku/resources/:id
Request Body: none
Response Status: 200

 kensa test provision
Testing POST /heroku/resources
  Check response [PASS]
  Check valid JSON [PASS]
  Check authentication [PASS]
Testing response
  Check contains an id [PASS]
Testing config data
  Check is a hash [PASS]
  Check all config keys were previously defined in the manifest [PASS]
  Check all config values are strings [PASS]
done.