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

Fix some scoping text #307

Merged
merged 1 commit into from
Oct 3, 2017
Merged

Conversation

duglin
Copy link
Contributor

@duglin duglin commented Sep 1, 2017

  • plan_id's are globally unique, not scoped to the service
  • I also fixed it so that we don't place requirements on the usage of IDs
    since that isn't necessary. Only the creation of the ID should state
    things like "its globally unique" or "must be non-empty string".
    The users of that ID can't control
    that aspect of it. However, we can control where the ID comes from so
    I added text to say things like "it MUST be the ID of a previously
    provisioned service".

Signed-off-by: Doug Davis dug@us.ibm.com

@cfdreddbot
Copy link

Hey duglin!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

@angarg12
Copy link
Contributor

angarg12 commented Sep 4, 2017

The OSBAPI website seems to be down and that is making the build fail. Should we move images to this repo?

@angarg12
Copy link
Contributor

angarg12 commented Sep 4, 2017

LGTM

Approved with PullApprove

@duglin
Copy link
Contributor Author

duglin commented Sep 5, 2017

we need to switch our OSB API URLs to be http instead of https.

@duglin
Copy link
Contributor Author

duglin commented Sep 11, 2017

Rebased and ready for another round of reviews

@angarg12
Copy link
Contributor

angarg12 commented Sep 11, 2017

LGTM

Approved with PullApprove

1 similar comment
@mattmcneeney
Copy link
Contributor

mattmcneeney commented Sep 11, 2017

LGTM

Approved with PullApprove

- plan_id are globally unique, not scoped to the service
- I also fixed it so that we don't place requirements on the usage of IDs
  since that isn't necessary. Only the creation of the ID should state
  things like "its globally unique" or must be non-empty string.
  The users of that ID can't control
  that aspect of it. However, we can control where the ID comes from so
  I added text to say things like "it MUST be the ID of a previously
  provisioned service".

Signed-off-by: Doug Davis <dug@us.ibm.com>
@duglin
Copy link
Contributor Author

duglin commented Sep 18, 2017

rebased and ready for reviews

@angarg12
Copy link
Contributor

angarg12 commented Sep 18, 2017

LGTM

Approved with PullApprove

1 similar comment
@avade
Copy link
Contributor

avade commented Sep 21, 2017

LGTM

Approved with PullApprove

@duglin
Copy link
Contributor Author

duglin commented Sep 25, 2017

2 more reviews needed

@mattmcneeney
Copy link
Contributor

mattmcneeney commented Sep 26, 2017

LGTM

Approved with PullApprove

@duglin
Copy link
Contributor Author

duglin commented Oct 3, 2017

one more review needed

@pmorie
Copy link
Contributor

pmorie commented Oct 3, 2017

LGTM

Approved with PullApprove

@pmorie pmorie merged commit 81e4256 into openservicebrokerapi:master Oct 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants