Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service plan and params support #29

Closed
gberche-orange opened this issue Jun 13, 2018 · 0 comments
Closed

Service plan and params support #29

gberche-orange opened this issue Jun 13, 2018 · 0 comments
Labels
Milestone

Comments

@gberche-orange
Copy link
Member

gberche-orange commented Jun 13, 2018

As a service author, in order to support arbitrary params in my service, I need to receive content of arbitrary params in a format by bosh deployment can leverage.

Proposed solution: the coab-vars.yml file contains the open service broker api standardized input for both service provisionning and update.

---
deployment_name: "c_aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaa0"
instance_id: "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaa0"
service_id: "service_definition_id"
plan_id: "plan_guid"
context:
  platform: "cloudfoundry"
  user_guid: "user_guid1"
  space_guid: "space_guid1"
  organization_guid: "org_guid1"
parameters:
  cacheRatio: 0.8642
  cacheSizeMb: 10
  slowQuery: false
previous_values:
  plan_id: "previous_plan_guid"

Service authors can test in their models various content of the coab-vars.yml which will be safely ignored by COAB

To maintain security, Input validation is applied on the name and value of arbitrary params to prevent various injections (such as reading from credhub, spruce, file system injection, yml loading or reference expansions), and only alphabetical characters, numbers are supported

Out of scope: implement the GET endpoints.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant