-
Notifications
You must be signed in to change notification settings - Fork 231
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
Support binding parameters #1987
Conversation
0483125
to
4603af8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just some passing thoughts.
ctrl.serviceClass = ctrl.serviceClasses[instance.spec.serviceClassName]; | ||
ctrl.serviceClassName = instance.spec.serviceClassName; | ||
ctrl.plan = BindingService.getPlanForInstance(instance, ctrl.serviceClass); | ||
ctrl.parameterSchema = _.get(ctrl.plan, 'alphaBindingCreateParameterSchema'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They don't come up too often, but do you think we ever need to doc these alpha
kinds of properties with a TODO
of FIXME
? Last I remember was the osb
prefixes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely reasonable. We've been trying to track the changes in the card because there are so many coming:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, that works for me. Something like FIXME: API ALPHA
could be a nice way to search, but might not be worth it if already tracked like the Trello.
ctrl.nextTitle = 'Bind'; | ||
ctrl.nextTitle = bindParametersStep.hidden ? 'Bind' : 'Next >'; | ||
if (!selectionValidityWatcher) { | ||
selectionValidityWatcher = $scope.$watch("ctrl.selectionForm.$valid", function(isValid) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm tempted to suggest we start using a pattern of var scopeWatches = []
and a loop in $onDestroy
to deregister, just to make all of our components consistent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically the scope watches clean themselves up on destroy and don't need to be explicitly deregistered. I wonder if it's worth tracking them except in the cases where we want to disable / enable them on certain steps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah prob not so much. I think I'm pointlessly tracking one in the drawer, should prob nix it.
4603af8
to
13474e8
Compare
Adds bind parameters to overview "Create Binding" action and in context provision binding. Bumps origin-web-common 0.0.52 -> 0.0.53 Bumps origin-web-catalog 0.0.42 -> to 0.0.43 https://trello.com/c/Sws4p5jU
13474e8
to
096fc19
Compare
[merge] |
[Test]ing while waiting on the merge queue |
Evaluated for origin web console test up to 096fc19 |
Origin Web Console Test Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_web_console/141/) (Base Commit: 38eb4eb) (PR Branch Commit: 096fc19) |
[merge] |
Evaluated for origin web console merge up to 096fc19 |
Origin Web Console Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin_web_console/134/) (Base Commit: a6bf807) (PR Branch Commit: 096fc19) |
https://trello.com/c/Sws4p5jU
Requires openshift/origin-web-common#163
Bumps origin-web-common 0.0.52 -> 0.0.53
Bumps origin-web-catalog 0.0.42 -> to 0.0.43
which also
Fixes #1979
Fixes #2002