Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Codify how asynchronous provision and deprovision responses are handled in the service catalog controller #49

Closed
arschles opened this issue Nov 22, 2016 · 2 comments
Closed

Codify how asynchronous provision and deprovision responses are handled in the service catalog controller #49

arschles opened this issue Nov 22, 2016 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Milestone
MVP 2

Comments

@arschles
Copy link
Contributor

See https://github.com/kubernetes-incubator/service-catalog/pull/40/files#diff-7bc5ab85846e6317175a21b5acb68061R65

Acceptance criteria for this issue:

  • Documentation that describes how the controller should modify the status.state fields of relevant Kubernetes resources when it receives an asynchronous response
  • Documentation that describes, at a high level, what logic the controller should implement to handle async responses. This should include what state the controller may need to store internally
@arschles arschles added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 22, 2016
@arschles arschles mentioned this issue Nov 22, 2016
Merged
@pmorie pmorie added this to the Legos-1 milestone Jan 11, 2017
@pmorie pmorie mentioned this issue Jan 11, 2017
Closed
@pmorie pmorie modified the milestones: MVP 2, Legos-1 Mar 6, 2017
@pmorie
Copy link
Contributor

pmorie commented Mar 6, 2017

Moving this to MVP-2 since it didn't wind up being in scope for legos-1

@pmorie
Copy link
Contributor

pmorie commented Mar 13, 2017

Closing; dupe of #249

@pmorie pmorie closed this as completed Mar 13, 2017
jboyd01 pushed a commit to jboyd01/service-catalog that referenced this issue Mar 20, 2019
@openshift-merge-robot
Merge pull request kubernetes-retired#49 from jboyd01/owners
a958cae 
add jmrodri to OWNERS
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
MVP 2
Development

No branches or pull requests
2 participants
@arschles @pmorie