Skip to content

TEAMFOUR-154 Admin register clusters#178

Merged
sean-sq-chen merged 4 commits into
masterfrom
TEAMFOUR-154_admin_clusters
Apr 8, 2016
Merged

TEAMFOUR-154 Admin register clusters#178
sean-sq-chen merged 4 commits into
masterfrom
TEAMFOUR-154_admin_clusters

Conversation

@woodm1979
Copy link
Copy Markdown
Contributor

When an admin logs in, if no clusters are currently registered, they
should be taken to an overlay where they can add clusters. Once they
have added atleast one cluster they should see a list of the clusters
they've added. This table should include a remove button for each
cluster so it can be removed from the list.

When an admin logs in, if no clusters are currently registered, they
should be taken to an overlay where they can add clusters.  Once they
have added atleast one cluster they should see a list of the clusters
they've added.  This table should include a remove button for each
cluster so it can be removed from the list.
@woodm1979
Copy link
Copy Markdown
Contributor Author

This PR now supersedes #165 . There was something very wrong there regarding rebasing.

</div>
</div>
<div class="fixed-footer" ng-if="clusterRegistrationCtrl.overlay">
<span class="registration-notification" ng-if="clusterRegistrationCtrl.clusterInstanceModel.numValid > 0"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove this since we're not tracking numValid and it's not present in the mocks

After Kelly/Sean's changes to button styles, some of our buttons need to
be changed from default to primary.
@WAT-TeamFour
Copy link
Copy Markdown

From Jenkins: There was a test failure while running Jenkins tests.

var mockServiceInstance = { id: 1, name: 'cluster1', url:' cluster1_url' };
$httpBackend.expectDELETE('/api/service-instances/1').respond(200, '');
serviceInstance.remove(1);
serviceInstance.remove(mockServiceInstance);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line is confusing me, should it be:

var serviceInstance = { id: 1, name: 'cluster1', url:' cluster1_url' };
serviceInstanceModel.remove(serviceInstance);

Cleaning up a few nits: single-quotes on "use strict" and a poor
variable name in serviceInstance.model.spec.js
@WAT-TeamFour
Copy link
Copy Markdown

From Jenkins: There was a test failure while running Jenkins tests.

$httpBackend.expectDELETE('/api/service-instances/1').respond(200, '');
serviceInstance.remove(mockServiceInstance);
var serviceInstance = { id: 1, name: 'cluster1', url:' cluster1_url' };
serviceInstance.remove(serviceInstance);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh! There are two serviceInstance defined here. That's why I used mockServiceInstance :)

renaming mocks to have the same name as another variable in scope is a
bad thing.  Don't be dum.
@sean-sq-chen sean-sq-chen merged commit a867ca7 into master Apr 8, 2016
@sean-sq-chen sean-sq-chen deleted the TEAMFOUR-154_admin_clusters branch April 8, 2016 21:16
richard-cox pushed a commit that referenced this pull request Jan 30, 2018
App wall and App Env Var Updates
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.

4 participants