-
Notifications
You must be signed in to change notification settings - Fork 134
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
Reuse unbound routes #1223
Reuse unbound routes #1223
Conversation
KlapTrap
commented
Aug 17, 2017
- Allow users to attach already create routes within the applications space to an applicaiton.
- Will only list routes that are not already attached to the application.
- Fixed tests.
- Added test.
- Couldn't run e2e tests on my mac so going to cheekily run them via concourse.
* master: Fix style issue Persist app wall selection of cf/org/space in local storage (#1214) Add upgrade documentation for helm repository based installation (#1218) Fixed docker image name for all-in-one deployment (#1216) Use stable name for docker registry (#1220) Update CI piplines for environment (#1217) Fixes and changed select source radio button to select-input dropdown - Converted the select source radio button to a drop down (ready for more sources) - Split out more styles from deploy-step-source.scss - Fixed github userinput validation - Fixed display of cf ignore info for manually opened file/folders Deploy fixes, removed common session data, added delay to 'scanning' busy screen Started deploy step, a few minor bugs to work through WIP UX for source mostly works now. Still plenty of tidy up to do WIP Refactor/reduce deploy app service WIP - Move steps out into their own service - Move input sources out into seperate directives Split deploy destination + source step into two 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.
Looks good. There's a few minor points though (see inline).
Additionally if you add enough routes to show the 'show more' option and shrink the modal the existing route table shows a vertical scroll bar prematurely.
width: auto; | ||
} | ||
.control-label { | ||
margin-left: -15px; |
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.
Not sure this is needed? Would be a departure from the style of all other input fields
@@ -222,12 +222,11 @@ nav.secondary-nav { | |||
|
|||
&:hover { | |||
color: $navbar-hover-fg; | |||
background-color: $navbar-hover-bg; |
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.
These two background-color's are needed
@@ -7,6 +7,8 @@ | |||
.module('cloud-foundry.api') | |||
.run(registerApi); | |||
|
|||
var BASE_URL = '/pp/v1/proxy/v2/apps'; |
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.
In the past we've avoided making changes to 'api' files as they were originally auto-generated. Going forward I don't think there's much harm in re-factoring but we need to bear in mind we might auto-generate these files for v3 of the cf api.
@@ -25,6 +25,8 @@ | |||
*/ | |||
function Route(apiManager, modelUtils) { | |||
|
|||
var routesApi = apiManager.retrieve('cloud-foundry.api.Routes'); |
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.
We've had some issues in the past where the apiManager/modelManager cannot retrieve the objects when their host function is run first, so will grab them when needed. It's probably best to leave these as is.
* @constructor | ||
*/ | ||
function AddRouteServiceFactory(modelManager, frameworkAsyncTaskDialog) { | ||
function AddRouteServiceFactory(modelManager, frameworkAsyncTaskDialog, $q, appClusterRoutesService) { |
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.
As a general rule we try to put angular $ services first. This practise wasn't applied from start though so you may still find places where they appear anywhere
spaceGuid + | ||
'/routes?include-relations=domain,apps&inline-relations-depth=1&results-per-page=100'; | ||
|
||
var expectedRoutesRes = { |
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.
There's an old practise of placing large responses in *.mock.spec.js files. Think the original plan was to build up a library of calls. Here's it's ok but if there's multiple it may be best to move to route.model.spec.js
* master: Reuse unbound routes (#1223) Revert "Added ulimit note to development readme" Show services in app summary page, auto pick service plan in add service modal Changes following review If the value of a 'select-input' is a placeholder always translate Fix e2e Moved logic into specific cloud-foundry-hosting plugin Final bits n bobs - Switch logic from 'disable' flag to 'enable' (true by default) - Updated docs - Prooved cf push with/wuthout flag Fix e2e Disable the endpoint-dashboard at runtime if env var is present - Plugins can now add config to the console-info call - Add backend component to endpoint-dashboard -- If env var 'DISABLE_ENDPOINT_DASHBOARD' is present add 'disabled' to component config - Handle disabled dashboard in frontend.. -- Do not add to menu -- Do not redirect to dashboard if no endpoints present -- Remove from env.plugins - Fixed endpoint on logged in message for admin's when there are no connected endpoints - Speed up logged in process by making 3 calls async - Improved unit tests Testing concourse Added ulimit note to development readme
* master: Reuse unbound routes (#1223) Revert "Added ulimit note to development readme" Show services in app summary page, auto pick service plan in add service modal Changes following review If the value of a 'select-input' is a placeholder always translate Fix e2e Moved logic into specific cloud-foundry-hosting plugin Final bits n bobs - Switch logic from 'disable' flag to 'enable' (true by default) - Updated docs - Prooved cf push with/wuthout flag Fix e2e Disable the endpoint-dashboard at runtime if env var is present - Plugins can now add config to the console-info call - Add backend component to endpoint-dashboard -- If env var 'DISABLE_ENDPOINT_DASHBOARD' is present add 'disabled' to component config - Handle disabled dashboard in frontend.. -- Do not add to menu -- Do not redirect to dashboard if no endpoints present -- Remove from env.plugins - Fixed endpoint on logged in message for admin's when there are no connected endpoints - Speed up logged in process by making 3 calls async - Improved unit tests Testing concourse Added ulimit note to development readme