cloudfoundry / stratos Goto Github PK

Stratos: Web-based Management UI for Cloud Foundry and Kubernetes

License: Apache License 2.0

Shell 2.76% JavaScript 1.08% HTML 6.63% CSS 0.10% Go 15.25% Smarty 0.01% TypeScript 70.66% Dockerfile 0.04% SCSS 3.42% Mustache 0.07%

cloud-foundry stratos-ui paas angular console go kubernetes stratos golang javascript

stratos's Introduction

Stratos

Stratos is an Open Source Web-based UI (Console) for managing Cloud Foundry. It allows users and administrators to both manage applications running in the Cloud Foundry cluster and perform cluster management tasks.

Please visit our new documentation site. There you can discover

Our introduction, including quick start, contributing and troubleshooting guides.
How to deploy Stratos in a number of environments.
1. Cloud Foundry, as an application.
2. Kubernetes, using a Helm chart.
3. Docker, as a single container deploying all components.
Configuring advanced features such a Single Sign On and Cloud Foundry 'invite to org'.
Guides for developers.
How to extend Stratos functionality and apply a custom theme.

Acknowledgements

Tested with Browserstack

License

The work done has been licensed under Apache License 2.0. The license file can be found here.

stratos's People

Contributors

Stargazers

Watchers

Forkers

hlyani hhio618 comdaze paroxp chrisfarms wbean1 cafxx ronakbanka suse orange-cloudfoundry morika-t jnpacker abhilash07 norsig hpcloud jyriok andrewghobrial linuxbozo rohitcs079 grapeup govau jjnich mattcui edwardstudy hongtaegu jrthearchitect seronet-project rogeruiz xuejiaozhang colton-nicotera irfanhabib anilkumar1204 mogul adamsmithlitigation anynines qmacro fidelityinternational virtualadrian fruit37 sstasenco shashankreddysunkara devopssuren arne-sandberg boyang9527 songjinseok jaymccon chao-huang arthurhlt springernature github-38438-org databill86 patjones freakin miro-grapeup ediboko1980 ui-store 3v1lw1th1n hamzahamidi suseclee abdul-fs dystudio fourspaces laashub-soa todokku accenturerapid 18f songmash cyrano007 zinuga massimiliano76 joshisa iagotomas simplefinance giva01121 hcl-cloud-native-labs boriskarastanev mukaiguy cuhland ikapelyukhin kinjelom cannedfish isabella232 nwmac pg2000 gstackio answercn zuunlabs pandulis thquad maniacs-ops mook-as heavenn113 mukulk2020 bi1ty ambriel2016 dave4272-office shah-hassan-khan navyasuri guptanavdeep1983 cloud-gov

stratos's Issues

Add basic tooltips, where appropiate, to mat-icons

From @richard-cox on January 29, 2018 11:0

Now we have a growing range of icons (app wall, app summary pages, endpoints, etc) we're using some more obscure ones and overloading others. Some very small and basic tooltips should be used to guide the user. This seems to be an accepted material design pattern for icons - https://material.io/guidelines/components/tooltips.html#

Copied from original issue: SUSE#193

Cloud Foundry deployment has Javascript error

Deployment type

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)

Expected behavior

Given I follow the Cloud Foundry deployment steps
When I visit the application's URL
Then I see a login screen

Actual behavior

Given I follow the Cloud Foundry deployment steps
When I visit the application's URL
Then I see a blank browser window

And the Chrome Inspector shows

Steps to reproduce the behavior

git clone https://github.com/SUSE/stratos-ui.git
cd stratos-ui
cf push

(This happens whether or not I force the use of https in the manifest.)

Log output covering before error and any error statements

Logs are clean. See screenshots above for Javascript errors.

How to change the GUI of this application?

How to change the GUI of the application?
Is this an angular 1 or 2+ applications?

'copy:configjs' errors

Deployment type

[X ] Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)

Expected behaviour

Build succeeds

Actual behaviour

Build fails

Steps to reproduce the behavior

'cf push' from master

applications:
- name: console
  memory: 1G
  disk_quota: 1G
  host: console
  timeout: 180
  buildpack: https://github.com/SUSE/stratos-buildpack
  health-check-type: port
  stack: cflinuxfs2
  env:
    FORCE_ENDPOINT_DASHBOARD: true
  services:
    - console_db

Log output covering before error and any error statements

[21:32:52] Using gulpfile /tmp/app/gulpfile.js
[21:32:52] Starting 'clean'...
[21:32:52] Finished 'clean' after 21 ms
[21:32:52] Starting 'clean:dist'...
[21:32:52] Finished 'clean:dist' after 18 μs
[21:32:53] Using gulpfile /tmp/app/gulpfile.js
[21:32:53] Starting 'build'...
[21:32:53] Starting 'clean'...
[21:32:53] Finished 'clean' after 18 ms
[21:32:53] Starting 'prepare-frontend'...
[21:32:54] Finished 'prepare-frontend' after 898 ms
[21:32:54] Starting 'copy:configjs'...
[21:32:54] Starting 'copy:bowerjs'...
[21:33:02] 'copy:configjs' errored after 8.77 s
[21:33:02] Error: Unknown system error -122: Unknown system error -122, mkdir '/tmp/app/dist'
    at Error (native)
[21:33:02] 'build' errored after 9.69 s
[21:33:02] Error in plugin 'run-sequence(copy:configjs)'
Message:
    Unknown system error -122: Unknown system error -122, mkdir '/tmp/app/dist'
Details:
    errno: -122
    code: Unknown system error -122
    syscall: mkdir
    path: /tmp/app/dist
Stack:
Error: Unknown system error -122: Unknown system error -122, mkdir '/tmp/app/dist'
    at Error (native)
[21:33:07] 'copy:bowerjs' errored after 13 s
[21:33:07] Error: Unknown system error -122: Unknown system error -122, mkdir '/tmp/app/dist'
    at Error (native)
npm ERR! Linux 4.4.0-1027-gke
npm ERR! argv "/tmp/node6.11.3/node-v6.11.3-linux-x64/bin/node" "/tmp/node6.11.3/node-v6.11.3-linux-x64/bin/npm" "run" "build"
npm ERR! node v6.11.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] build: `gulp clean:dist && gulp`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] build script 'gulp clean:dist && gulp'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the stratos-ui package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp clean:dist && gulp
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs stratos-ui
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls stratos-ui
npm ERR! There is likely additional logging output above.
npm ERR! Linux 4.4.0-1027-gke
npm ERR! argv "/tmp/node6.11.3/node-v6.11.3-linux-x64/bin/node" "/tmp/node6.11.3/node-v6.11.3-linux-x64/bin/npm" "run" "build"
npm ERR! node v6.11.3
npm ERR! npm  v3.10.10
npm ERR! path npm-debug.log.1142109357
npm ERR! code Unknown system error -122
npm ERR! errno -122
npm ERR! syscall open
npm ERR! Unknown system error -122: Unknown system error -122, open 'npm-debug.log.1142109357'
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR!     /tmp/app/npm-debug.log
Failed to compile droplet
Exit status 223
Staging failed: Exited with status 223
Destroying container
Successfully destroyed container

Deploy application: Handle apps where the manifest lives outside of repo

As a follow on from #1442 we should also look at catering for apps where the manifest is not in the repo. Usually this is handled by cf push -f .
Suggestion..

Provide a way for the user to specify a manifest within the deploy process
save manifest where we fetch the repo

BOSH and CFCR Support?

Hi,

Looks good ...

One quick Question, does the UI Support the BOSH Director Deployments Self or just the final CF?
I.e. Can we use it to introspect CFCR Deployments?

Many Thanks.. Happy X-Mas

Json schema support for service instance/binding

Detailed Description

The Open Service Broker API enables broker authors to specify JSON schema to help client UIs in providing user friendly support for arbitrary params in service instances and service bindings requests. Orange would like to contribute such support when a JSON schema is specified in the service broker catalog: this would generate a form enabling users to discover supported arbitrary param names, and validate params value before submission.

Context

There are an increasing number of service brokers offering arbitrary params, in particular in the context of on-demand dedicated data services (such as cluster sizes, or specific tunings). This feature will provide friendly support for such services.

Possible Implementation

The JSon schema is served by CA API https://apidocs.cloudfoundry.org/280/service_plans/retrieve_a_particular_service_plan.html

There as multiple JSON schema libraries http://json-schema.org/implementations.html along with JS UI generators

/CC @hamzahamidi

Error with the latest release (Maybe Angular1.6 )

Deployment type

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
[ x] Other (please provide below)

Expected behaviour

Actual behaviour

When running the command gulp dev I get no error on the console but nothing appears in chrome.
In chrome Dev tools I get this in the console:

Steps to reproduce the behavior

Log output covering before error and any error statements

gulp dev
[15:05:13] Using gulpfile ~/stratos-ui/gulpfile.js
[15:05:13] Starting 'dev-build'...
[15:05:13] Starting 'clean'...
[15:05:14] Finished 'clean' after 1.04 s
[15:05:14] Starting 'prepare-frontend'...
[15:05:15] Finished 'prepare-frontend' after 508 ms
[15:05:15] Starting 'copy:configjs'...
[15:05:15] Starting 'copy:bowerjs'...
[15:05:15] Finished 'copy:configjs' after 74 ms
[15:05:15] Finished 'copy:bowerjs' after 75 ms
[15:05:15] Starting 'copy:js'...
[15:05:20] Finished 'copy:js' after 5.42 s
[15:05:20] Starting 'copy:lib'...
[15:05:21] Finished 'copy:lib' after 368 ms
[15:05:21] Starting 'css:generate'...
[15:05:23] Finished 'css:generate' after 1.89 s
[15:05:23] Starting 'css'...
[15:05:24] Finished 'css' after 920 ms
[15:05:24] Starting 'i18n'...
[15:05:24] Finished 'i18n' after 41 ms
[15:05:24] Starting 'dev-template-cache'...
[15:05:24] Finished 'dev-template-cache' after 2.7 ms
[15:05:24] Starting 'copy:html'...
[15:05:27] Finished 'copy:html' after 3.13 s
[15:05:27] Starting 'copy:assets'...
[15:05:27] Finished 'copy:assets' after 37 ms
[15:05:27] Starting 'i18n'...
[15:05:27] Starting 'copy:index'...
[15:05:27] Finished 'copy:index' after 6.71 ms
[15:05:27] Finished 'i18n' after 37 ms
[15:05:27] Starting 'inject:index'...
[15:05:27] gulp-inject 305 files into index.html.
[15:05:27] Finished 'inject:index' after 309 ms
[15:05:27] Finished 'dev-build' after 14 s
[15:05:27] Starting 'dev'...
[15:05:27] Starting 'browsersync'...
[15:05:27] Serving HTTPS with the default BrowserSync certificate
[15:05:27] Proxying API requests to: https://ows2.cf.nd-paas.itn.ftgroup/pp
[15:05:27] Finished 'dev' after 302 ms
[Browsersync] Access URLs:
 --------------------------------------
       Local: https://localhost:3100
    External: https://10.194.9.216:3100
 --------------------------------------
          UI: http://localhost:3001
 UI External: http://10.194.9.216:3001
 --------------------------------------
[Browsersync] Serving files from: ./bower_components
[Browsersync] Serving files from: ./dist
[15:05:28] Finished 'browsersync' after 384 ms
[15:05:28] Starting 'watch'...
[15:05:28] Finished 'watch' after 414 ms```

UI with multiple endpoints?

Hi,

We have multiple cloud foundry environements. Is it possible to get the data of all the environments by providing the api's in single dashboard?

Thanks,
Akhilesh Appana

Add support for inviting users to a CF Org

Use case:

I'm an org manager, we have a new starter in the team, I want to invite them to my org in CloudFoundry via stratos.

'copy:bowerjs' errors - stratos won't build as app

Deployment type

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)

Expected behaviour

console is deployed

Actual behaviour

/tmp/tmp.pmmHSUMuqy/src/golang.org/x/sys/windows/ztypes_windows.go exists, skipping...
/tmp/tmp.pmmHSUMuqy/src/golang.org/x/sys/windows/ztypes_windows_386.go exists, skipping...
/tmp/tmp.pmmHSUMuqy/src/golang.org/x/sys/windows/ztypes_windows_amd64.go exists, skipping...
[03:52:05] Finished 'dedup-vendor' after 2.64 s

[email protected] build /tmp/app
gulp clean:dist && gulp
[03:52:07] Using gulpfile /tmp/app/gulpfile.js
[03:52:07] Starting 'clean'...
[03:52:07] Finished 'clean' after 20 ms
[03:52:07] Starting 'clean:dist'...
[03:52:07] Finished 'clean:dist' after 17 μs
[03:52:08] Using gulpfile /tmp/app/gulpfile.js
[03:52:08] Starting 'build'...
[03:52:08] Starting 'clean'...
[03:52:08] Finished 'clean' after 21 ms
[03:52:08] Starting 'prepare-frontend'...
[03:52:09] Finished 'prepare-frontend' after 1.14 s
[03:52:09] Starting 'copy:configjs'...
[03:52:09] Starting 'copy:bowerjs'...
[03:52:18] 'copy:configjs' errored after 9.08 s
[03:52:18] Error: Unknown system error -122: Unknown system error -122, mkdir '/tmp/app/dist'
at Error (native)
[03:52:18] 'build' errored after 10 s
[03:52:18] Error in plugin 'run-sequence(copy:configjs)'
Message:
Unknown system error -122: Unknown system error -122, mkdir '/tmp/app/dist'
Details:
errno: -122
code: Unknown system error -122
syscall: mkdir
path: /tmp/app/dist
Stack:
Error: Unknown system error -122: Unknown system error -122, mkdir '/tmp/app/dist'
at Error (native)
[03:52:23] 'copy:bowerjs' errored after 14 s
[03:52:23] Error: Unknown system error -122: Unknown system error -122, mkdir '/tmp/app/dist'
at Error (native)
npm ERR! Linux 4.4.0-1027-gke
npm ERR! argv "/tmp/node6.11.3/node-v6.11.3-linux-x64/bin/node" "/tmp/node6.11.3/node-v6.11.3-linux-x64/bin/npm" "run" "build"
npm ERR! node v6.11.3
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] build: gulp clean:dist && gulp
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script 'gulp clean:dist && gulp'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the stratos-ui package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp clean:dist && gulp
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs stratos-ui
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls stratos-ui
npm ERR! There is likely additional logging output above.
npm ERR! Linux 4.4.0-1027-gke
npm ERR! argv "/tmp/node6.11.3/node-v6.11.3-linux-x64/bin/node" "/tmp/node6.11.3/node-v6.11.3-linux-x64/bin/npm" "run" "build"
npm ERR! node v6.11.3
npm ERR! npm v3.10.10
npm ERR! path npm-debug.log.341517281
npm ERR! code Unknown system error -122
npm ERR! errno -122
npm ERR! syscall open
npm ERR! Unknown system error -122: Unknown system error -122, open 'npm-debug.log.341517281'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
npm ERR! /tmp/app/npm-debug.log
Failed to compile droplet
Exit status 223
Staging failed: Exited with status 223
Destroying container
Successfully destroyed container

FAILED
Error restarting application: BuildpackCompileFailed

Steps to reproduce the behavior

git clone https://github.com/SUSE/stratos-ui.git
cf push

Log output covering before error and any error statements

Insert log here

Chinese localization

I have internationalization needs, I added some stratos-ui Simplified Chinese support, can I submit the code?

Log stream should sort messages by timestamp

From slack:

Hi All - I noticed stratos offerings a display for streaming logs. If you don’t already it would be a good idea to sort the logs based on timestamp. This is helpful to app developers for debugging purposes. I posted some notes about common techniques for this in cf-dev but if you need further help the #loggregator team is happy to assist.

We should ensure that the log messages are sorted by timestamp.

Create a table module for all of our table related code.

From @KlapTrap on January 29, 2018 15:11

We have a lot of components in the shared module, breaking these up will make the app more manageable - let's start with the table components.

Copied from original issue: SUSE#195

Error 400 Bad Request with Log stream & SSH when deploying in PWS

Deployment type

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)

Expected behaviour

Actual behaviour

Error 400 Bad Request with log stream & SSH

Steps to reproduce the behavior

I just deployed the UI in PWS with cf push

Log output covering before error and any error statements

Error 400 Bad Request

Speed up time-to-content and support low-Javascript clients

Detailed Description

The UI takes a while to appear on first load, and any problems with Javascript (whether due to the content served or to the capabilities of the client device) render the Stratos UI unusable.

Modern apps address this by rendering page content both server- and client-side, so that the client gets a full HTML page with each request, and fallback behavior without JS is to reload the page with each click. This delivers both a quick first-load/reload experience and makes the UI usable by more users on more client apps/devices.

Context

Speed is a feature, particularly when it's subjective or degrades over high-latency connections.
Government deployments (eg cloud.gov, cloud.gov.au) need to ensure services are accessible to low-end devices wherever possible.

Possible Implementation

This would be achievable by upgrading to the latest version of AngularJS and using Angular Universal. Upgrading Angular brings other benefits for features and maintainability, of course!

Double clicking on show/hide password `eye` button, something on the screen are selected.

Updates to deploy

From @richard-cox on January 30, 2018 14:52

Deployment info is missing for apps deployed by v1 (?)
Review the log viewer sizing
- Lots of wasted space either size
- Width can jump about given content. For example on a small screen the following line unexpectedly increased the size of the log viewer and window
  [file:///tmp/buildpacks/1fee4c454be29fdb221ca7496aafdac2/dependencies/https___buildpacks.cloudfoundry.org_dependencies_node_node-6.10.2-linux-x64-9f48b587.tgz]

Copied from original issue: SUSE#200

Failed to Deploy App (ERR panic: interface conversion: interface {} is string, not float64)

Deployment type

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)

Expected behaviour

Start the app.

Actual behaviour

Failed to start app.

Steps to reproduce the behavior

$ git clone https://github.com/SUSE/stratos-ui.git
$ cd stratos-ui
$ vi manifest.yml

$ cf login -a api.<SYSTEM-DOMAIN> --skip-ssl-validation
$ cf create-service Mysql-DB Mysql-Plan1-5con mysql-console
$ cf push

applications:
- name: console
  memory: 256M
  disk_quota: 256M
  host: console
  timeout: 180
  buildpack: https://github.com/SUSE/stratos-buildpack
  health-check-type: port
  env:
    CF_API_URL: https://api.<SYSTEM-DOMAIN>
    CF_API_FORCE_SECURE: true
    FORCE_ENDPOINT_DASHBOARD: true
  services:
  - mysql-console

Log output covering before error and any error statements

2017-11-20T16:04:01.41+0900 [CELL/0]     OUT Starting health monitoring of container
2017-11-20T16:04:01.44+0900 [APP/0]      OUT Starting Stratos UI
2017-11-20T16:04:01.44+0900 [APP/0]      OUT Attempting to migrate database
2017-11-20T16:04:01.44+0900 [APP/0]      OUT Attempting to parse VCAP_SERVICES
2017-11-20T16:04:01.44+0900 [APP/0]      OUT Found 1 database service instances
2017-11-20T16:04:01.44+0900 [APP/0]      OUT Using first database service instance: mysql-stratos
2017-11-20T16:04:01.44+0900 [APP/0]      OUT Parsing MySQL db config
2017-11-20T16:04:01.44+0900 [APP/0]      OUT Migrating mysql instance on 172.16.20.12
2017-11-20T16:04:01.45+0900 [APP/0]      OUT ========================
2017-11-20T16:04:01.45+0900 [APP/0]      OUT Stratos UI DB Migration
2017-11-20T16:04:01.45+0900 [APP/0]      OUT ========================
2017-11-20T16:04:01.45+0900 [APP/0]      OUT Migrations dir: deploy/db/migrations
2017-11-20T16:04:01.45+0900 [APP/0]      OUT Current 20170829154900
2017-11-20T16:04:01.45+0900 [APP/0]      OUT Target: 20170829154900
2017-11-20T16:04:01.45+0900 [APP/0]      OUT Running migrations ....
2017-11-20T16:04:01.45+0900 [APP/0]      OUT Skipping migration: 20170818120003
2017-11-20T16:04:01.45+0900 [APP/0]      OUT Skipping migration: 20170818162837
2017-11-20T16:04:01.45+0900 [APP/0]      OUT Skipping migration: 20170829154900
2017-11-20T16:04:01.45+0900 [APP/0]      OUT No migrations to run.
2017-11-20T16:04:01.45+0900 [APP/0]      OUT Database successfully migrated
2017-11-20T16:04:01.45+0900 [APP/0]      OUT Starting...
2017-11-20T16:04:01.45+0900 [APP/0]      OUT INFO[Mon Nov 20 07:04:01 UTC 2017] Initialization started.                      
2017-11-20T16:04:01.45+0900 [APP/0]      OUT INFO[Mon Nov 20 07:04:01 UTC 2017] Loaded configuration from file: ./config.properties 
2017-11-20T16:04:01.45+0900 [APP/0]      OUT INFO[Mon Nov 20 07:04:01 UTC 2017] Configuration loaded.                        
2017-11-20T16:04:01.45+0900 [APP/0]      OUT INFO[Mon Nov 20 07:04:01 UTC 2017] Console Version loaded: 0.9.7                
2017-11-20T16:04:01.45+0900 [APP/0]      OUT INFO[Mon Nov 20 07:04:01 UTC 2017] HTTP client initialized.                     
2017-11-20T16:04:01.45+0900 [APP/0]      OUT INFO[Mon Nov 20 07:04:01 UTC 2017] Encryption key set.                          
2017-11-20T16:04:01.45+0900 [APP/0]      OUT INFO[Mon Nov 20 07:04:01 UTC 2017] Found 1 database service instances           
2017-11-20T16:04:01.45+0900 [APP/0]      OUT INFO[Mon Nov 20 07:04:01 UTC 2017] Using first database service instance: mysql-stratos 
2017-11-20T16:04:01.45+0900 [APP/0]      ERR panic: interface conversion: interface {} is string, not float64
2017-11-20T16:04:01.45+0900 [APP/0]      ERR goroutine 1 [running]:
2017-11-20T16:04:01.45+0900 [APP/0]      ERR github.com/SUSE/stratos-ui/components/app-core/backend/datastore.findDatabaseConfig(0xc420081c20, 0xc42008ca00, 0x240)
2017-11-20T16:04:01.45+0900 [APP/0]      ERR 	/tmp/tmp.eQalrwh5RW/src/github.com/SUSE/stratos-ui/components/app-core/backend/datastore/database_cf_config.go:85 +0xda7
2017-11-20T16:04:01.45+0900 [APP/0]      ERR github.com/SUSE/stratos-ui/components/app-core/backend/datastore.ParseCFEnvs(0xc42008ca00, 0x1)
2017-11-20T16:04:01.45+0900 [APP/0]      ERR 	/tmp/tmp.eQalrwh5RW/src/github.com/SUSE/stratos-ui/components/app-core/backend/datastore/database_cf_config.go:44 +0x1ab
2017-11-20T16:04:01.45+0900 [APP/0]      ERR main.loadDatabaseConfig(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
2017-11-20T16:04:01.45+0900 [APP/0]      ERR 	/tmp/tmp.eQalrwh5RW/src/github.com/SUSE/stratos-ui/components/app-core/backend/main.go:330 +0x104
2017-11-20T16:04:01.45+0900 [APP/0]      ERR main.main()
2017-11-20T16:04:01.45+0900 [APP/0]      ERR 	/tmp/tmp.eQalrwh5RW/src/github.com/SUSE/stratos-ui/components/app-core/backend/main.go:101 +0x566
2017-11-20T16:04:01.45+0900 [APP/0]      OUT Exit status 2
2017-11-20T16:04:01.46+0900 [CELL/0]     OUT Exit status 0
2017-11-20T16:04:01.50+0900 [CELL/0]     OUT Creating container
2017-11-20T16:04:02.42+0900 [API/0]      OUT App instance exited with guid 39bd92de-8acd-4612-861f-c07607f8c852 payload: {"instance"=>"", "index"=>0, "reason"=>"CRASHED", "exit_description"=>"2 error(s) occurred:\n\n* 2 error(s) occurred:\n\n* Exited with status 2\n* cancelled\n* cancelled", "crash_count"=>2, "crash_timestamp"=>1511161465560971699, "version"=>"09cddf13-dbbd-4fe2-a169-879a43e626c7"}

The deployed version not updating in Chrome

Deployment type

[ x] Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)

Expected behaviour

I made some changes in GUI but it's not updating.

Actual behaviour

Chrome isn't updating the changes. I had to use incognito mode.
It's updating for firefow though.

Steps to reproduce the behavior

cf push

Log output covering before error and any error statements

Insert log here

Create error and block state for card list views

From @KlapTrap on January 29, 2018 17:54

See SUSE#196 && #29

Copied from original issue: SUSE#198

Log viewer improvement + bug

From @richard-cox on January 30, 2018 14:53

Configurable display of pause button.. to be used in deploy app log stream instance
Looks like new lines might not be honoured in output. See the last line of a successful deploy in v1 and v2

Copied from original issue: SUSE#201

Enable to re-deploy github/remote deployed apps

It would be nice to trigger a re-deploy from the UI, enabling stratos managed apps to be updated on demand

Context

Mostly, demonstrating the functionality of Stratos and adding value in the UI, but in the event of the need to trigger manually a rebuild from a source that is not currently available to push with cf push.

When not being able to access source, the build env and needing to push code that is more static. Or just because we need to quickly push from a branch.

Possible Implementation

it would be nice to provide a re-deploy button where the user us reminded where that application is hosted and which branch is being used to re-deploy. Additionally, if there are several replicas/instances, then perform a rolling rebuild vs a destructive rebuild.

Helm Chart: Randomize passwords

Currently, we are dragging a "changeme" password collection in the helm chart, could we adopt a randomizer to set the passwords? Perhaps something like the scf team is doing.

Disable selection and actions for table rows in the blocked state

From @KlapTrap on January 29, 2018 17:53

See #196 && #29

Copied from original issue: SUSE#197

Support UAA login UX directly

Currently, Stratos UI has its own login screen and authenticates using the UAA APIs.

It should support using the UAA's login UX directly for authentication.

Issue when Working on the backend component like a dev

Deployment type

(select the type below by replacing the space with an x)

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)
Working on the backend component like a dev

Expected behaviour

Actual behaviour

When I go to https://localhost:413/ I get error 404 not found

Steps to reproduce the behavior

Set up developer certs
Execute deploy/tools/generate_cert.sh
Copy portal-proxy-output/dev-certs to ./
Update build/dev_config.json with "localDevBuild": true
Run gulp local-dev-build
cd ./outputs
Run gulp build-backend
Update config.propeties and ensure that the UAA points to a valid instance & the CONSOLE_CLIENT and CONSOLE_ADMIN_SCOPE are valid in the UAA instance
Run portal-proxy

Log output covering before error and any error statements

~/stratos-ui/outputs$ ./portal-proxy
INFO[Fri Dec 15 11:23:40 CET 2017] Initialization started.
INFO[Fri Dec 15 11:23:40 CET 2017] Loaded configuration from file: ./config.properties
INFO[Fri Dec 15 11:23:40 CET 2017] Configuration loaded.
INFO[Fri Dec 15 11:23:40 CET 2017] Console Version loaded: 0.9.9-fbf2e0d
INFO[Fri Dec 15 11:23:40 CET 2017] HTTP client initialized.
INFO[Fri Dec 15 11:23:40 CET 2017] Encryption key set.
INFO[Fri Dec 15 11:23:40 CET 2017] NewDatabaseConnectionParametersFromConfig
INFO[Fri Dec 15 11:23:40 CET 2017] Created database schema for SQLite database
INFO[Fri Dec 15 11:23:40 CET 2017] Database appears to now be available.
INFO[Fri Dec 15 11:23:40 CET 2017] Proxy database connection pool created.
INFO[Fri Dec 15 11:23:40 CET 2017] Creating SQLite session store
INFO[Fri Dec 15 11:23:40 CET 2017] Proxy session store initialized.
INFO[Fri Dec 15 11:23:40 CET 2017] Proxy initialization complete.
INFO[Fri Dec 15 11:23:40 CET 2017] Console has been setup with the following settings: &{UAAEndpoint:http://*** ConsoleAdminScope:http://*** ConsoleClient:http://*** ConsoleClientSecret: SkipSSLValidation:true IsSetupComplete:false}
INFO[Fri Dec 15 11:23:40 CET 2017] Console is intialised with the following settings: &{UAAEndpoint:http://*** ConsoleAdminScope:http://*** ConsoleClient:http://*** ConsoleClientSecret: SkipSSLValidation:true IsSetupComplete:false}
INFO[Fri Dec 15 11:23:40 CET 2017] Loaded plugin: {LibraryPath:cloud-foundry.so PluginPath:cloud-foundry PluginName:cloud-foundry}
INFO[Fri Dec 15 11:23:40 CET 2017] Loaded plugin: {LibraryPath:cf-app-ssh.so PluginPath:cf-app-ssh PluginName:cf-app-ssh}
INFO[Fri Dec 15 11:23:40 CET 2017] Loaded plugin: {LibraryPath:cf-app-push.so PluginPath:cf-app-push PluginName:cf-app-push}
INFO[Fri Dec 15 11:23:40 CET 2017] Loaded plugin: {LibraryPath:user-info.so PluginPath:user-info PluginName:user-info}
INFO[Fri Dec 15 11:23:40 CET 2017] User Info component loaded
INFO[Fri Dec 15 11:23:40 CET 2017] Initialised general plugins.
INFO[Fri Dec 15 11:23:40 CET 2017] Starting HTTPS Server at address: :443
WARN[Fri Dec 15 11:23:40 CET 2017] Failed to start HTTP/S server%!(EXTRA *net.OpError=listen tcp :443: bind: permission denied)
INFO[Fri Dec 15 11:23:40 CET 2017] Unable to start proxy!
INFO[Fri Dec 15 11:23:40 CET 2017] --- Setting up sessionStore cleanup
INFO[Fri Dec 15 11:23:40 CET 2017] --- Closing sessionStore
INFO[Fri Dec 15 11:23:40 CET 2017] --- Closing databaseConnectionPool

When running with sudo

/stratos-ui/outputs$ sudo ./portal-proxy
INFO[Fri Dec 15 11:24:29 CET 2017] Initialization started.
INFO[Fri Dec 15 11:24:29 CET 2017] Loaded configuration from file: ./config.properties
INFO[Fri Dec 15 11:24:29 CET 2017] Configuration loaded.
INFO[Fri Dec 15 11:24:29 CET 2017] Console Version loaded: 0.9.9-fbf2e0d
INFO[Fri Dec 15 11:24:29 CET 2017] HTTP client initialized.
INFO[Fri Dec 15 11:24:29 CET 2017] Encryption key set.
INFO[Fri Dec 15 11:24:29 CET 2017] NewDatabaseConnectionParametersFromConfig
INFO[Fri Dec 15 11:24:29 CET 2017] Created database schema for SQLite database
INFO[Fri Dec 15 11:24:29 CET 2017] Database appears to now be available.
INFO[Fri Dec 15 11:24:29 CET 2017] Proxy database connection pool created.
INFO[Fri Dec 15 11:24:29 CET 2017] Creating SQLite session store
INFO[Fri Dec 15 11:24:29 CET 2017] Proxy session store initialized.
INFO[Fri Dec 15 11:24:29 CET 2017] Proxy initialization complete.
INFO[Fri Dec 15 11:24:29 CET 2017] Console has been setup with the following settings: &{UAAEndpoint:http://*** ConsoleAdminScope:http://*** ConsoleClient:http://*** ConsoleClientSecret: SkipSSLValidation:true IsSetupComplete:false}
INFO[Fri Dec 15 11:24:29 CET 2017] Console is intialised with the following settings: &{UAAEndpoint:http://*** ConsoleAdminScope:http://*** ConsoleClient:http://*** ConsoleClientSecret: SkipSSLValidation:true IsSetupComplete:false}
INFO[Fri Dec 15 11:24:29 CET 2017] Loaded plugin: {LibraryPath:cloud-foundry.so PluginPath:cloud-foundry PluginName:cloud-foundry}
INFO[Fri Dec 15 11:24:29 CET 2017] Loaded plugin: {LibraryPath:cf-app-ssh.so PluginPath:cf-app-ssh PluginName:cf-app-ssh}
INFO[Fri Dec 15 11:24:29 CET 2017] Loaded plugin: {LibraryPath:cf-app-push.so PluginPath:cf-app-push PluginName:cf-app-push}
INFO[Fri Dec 15 11:24:29 CET 2017] Loaded plugin: {LibraryPath:user-info.so PluginPath:user-info PluginName:user-info}
INFO[Fri Dec 15 11:24:29 CET 2017] User Info component loaded
INFO[Fri Dec 15 11:24:29 CET 2017] Initialised general plugins.
INFO[Fri Dec 15 11:24:29 CET 2017] Starting HTTPS Server at address: :443
{"time":"2017-12-15T11:25:11+01:00","remote_ip":"::1","method":"GET","uri":"/","status":404, "latency":16,"latency_human":"16.215µs","bytes_in":0,"bytes_out":9}
{"time":"2017-12-15T11:25:11+01:00","remote_ip":"::1","method":"GET","uri":"/robots.txt","status":404, "latency":17,"latency_human":"17.135µs","bytes_in":0,"bytes_out":9}
{"time":"2017-12-15T11:25:11+01:00","remote_ip":"::1","method":"GET","uri":"/favicon.ico","status":404, "latency":18,"latency_human":"18.463µs","bytes_in":0,"bytes_out":9}

Detailed Description

Context

Possible Implementation

Text illisible login form autocomplete chrome

Deployment type

[ x] Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)

Expected behaviour

Actual behaviour

Steps to reproduce the behavior

When trying to Fill out forms automatically with chrome, the text becomes illisible

Log output covering before error and any error statements

Insert log here

Reset app event pagination automatically

From @richard-cox on January 29, 2018 14:46

Editing application variables creates app events. We should clear the app event pagination section when app variables successfully change. There could be other places were we should do this as well (start/stop app?)
Alternatively we could reset it every time we come to the page? Or dispatch the update event and show cached info first?

Copied from original issue: SUSE#194

Deployment on CF doesn't support multi-buildpack

Deployment type

[X ] Cloud Foundry Application (cf push)

Expected behaviour

According to the doc, enable-endpoints-dashboard-to-register-additional-cloud-foundry-endpoints show a sample using multi-buildpack. But current CF manifest is using stratos-buildpack

Actual behaviour

Application failed to start at staging

Steps to reproduce the behavior

Use multi-builpack instead of statos-buildpack

Log output covering before error and any error statements

 2017-10-13T14:21:53.67+0000 [STG/0] OUT Staging...
 2017-10-13T14:22:02.60+0000 [STG/0] OUT -----> Download go 1.9
 2017-10-13T14:22:06.75+0000 [STG/0] OUT -----> Running go build compile
 2017-10-13T14:22:08.35+0000 [STG/0] OUT -----> Multi Buildpack version 1.0.1
 2017-10-13T14:22:08.35+0000 [STG/0] OUT        **ERROR** A multi-buildpack.yml file must be provided at your app root to use this buildpack.
 2017-10-13T14:22:08.35+0000 [STG/0] ERR Failed to compile droplet
 2017-10-13T14:22:08.35+0000 [STG/0] OUT Exit status 223

Deploy application: Enable deploying from private Git repositories

Deployment type

(select the type below by replacing the space with an x)

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)

Expected behaviour

As a UI user I want to be able to deploy an application contained in a Git repository that requires authentication (username and password explicitly provided by the user)
As a UI user I want to be able to deploy an application contained in a Git repository that requires authentication (username and password of the currently logged-in user)

Actual behaviour

As a UI user I can deploy only applications contained in a public Git repository (i.e. a repository with no authentication)

Steps to reproduce the behavior

Click on "deploy application"
Notice that the only supported options are "deploy from public github repo", "deploy from public Git repo" and "deploy from local folder/file"

Detailed Description

The deploy application UI should allow users to (optionally) specify the credentials to use when authenticating to the remote Git repository. The UI should then use these credentials when pulling the repository.

Context

In corporate environments most repositories require authentication.

Possible Implementation

Add .cf-extensions to your repo to be listed in cloudfoundry-incubator.cf-extensions

Add .cf-extensions file to your repo so that it shows correctly in the CF-Extensions hub and catalog.

{
  "lead_company": "ADD LEAD COMPANY HERE",
  "contact_email": "[email protected]",
  "description": "ADD DESCRIPTION HERE",
  "slack_channel": "#add-slack-channel-here",
  "tracker_url": "https://www.pivotaltracker.com",
  "proposal_url": "https://docs.google.com/document/d/1cpyBmds7WYNLKO1qkjhCdS8bNSJjWH5MqTE-h1UCQkQ/edit?usp=sharing",
  "proposed_date": "2018-01-19T17:37:49-08:00"
}

lead_company: ADD LEAD COMPANY HERE
contact_email: [email protected]
description: ADD DESCRIPTION HERE
slack_channel: '#add-slack-channel-here'
tracker_url: https://www.pivotaltracker.com
proposal_url: https://docs.google.com/document/d/1cpyBmds7WYNLKO1qkjhCdS8bNSJjWH5MqTE-h1UCQkQ/edit?usp=sharing
proposed_date: 2018-01-19T17:37:49-08:00

This is a JSON or YAML formatted file. The default values in the file are for you to get started. You should edit to match your project's data.

For example, the field tracker_url should contain your project's tracker URL, and so on.

FINAL NOTES

You may also add two more optional fields: logo_url and icon_url pointing to images for your logo and icon respectively.

For best results your images should be in JPG or PNG file formats and their sizes around 200x300 pixels for logo and 32x32 pixels for icon.

After login button click, there is no feedback that credentials are being authenticating

A "loading" spinner should show while authentication request is still processing. This is especially noticeable when the request ends up timing out.

Additionally, the login button should be disabled until response received.

Staging fails when pushed from Windows

Deployment type

Cloud Foundry Application (cf push)

Expected behaviour

git clone stratos-ui repo locally on Windows 10
cd statros-ui
cf push
App starts and can be visited at https://console.bosh-lite.com

Actual behaviour

cf push fails on Windows 10 machine.
cf push succeeds if executed from within bosh-lite Vagrant box (Linux env.)

Steps to reproduce the behavior

See steps 1-3 of Expected Behaviour
Make sure core.autocrlf=true in git config -l

Log output covering before error and any error statements

   2017-10-24T14:01:57.55+0100 [API/0] OUT Created app with guid d03ee883-93b5-41a8-97a5-cb9c18f49f32
   2017-10-24T14:01:58.39+0100 [API/0] OUT Updated app with guid d03ee883-93b5-41a8-97a5-cb9c18f49f32 ({"route"=>"830ee275-4c3b-429c-96ee-e7a5527970f9", :verb=>"add", :relation=>"routes", :related_guid=>"830ee275-4c3b-429c-96ee-e7a5527970f9"})
   2017-10-24T14:02:25.80+0100 [API/0] OUT Uploading bits for app with guid d03ee883-93b5-41a8-97a5-cb9c18f49f32
   2017-10-24T14:02:36.97+0100 [API/0] OUT Creating build for app with guid d03ee883-93b5-41a8-97a5-cb9c18f49f32
   2017-10-24T14:02:37.06+0100 [API/0] OUT Updated app with guid d03ee883-93b5-41a8-97a5-cb9c18f49f32 ({"state"=>"STARTED"})
   2017-10-24T14:02:37.07+0100 [STG/0] OUT Creating container
   2017-10-24T14:02:37.39+0100 [STG/0] OUT Successfully created container
   2017-10-24T14:02:37.71+0100 [STG/0] OUT Downloading app package...
   2017-10-24T14:02:38.60+0100 [STG/0] OUT Downloaded app package (8.7M)
   2017-10-24T14:02:38.60+0100 [STG/0] OUT Staging...
   2017-10-24T14:02:40.41+0100 [STG/0] OUT Stratos UI Buildpack
   2017-10-24T14:02:40.41+0100 [STG/0] OUT -----> Stack cflinuxfs2
   2017-10-24T14:02:40.41+0100 [STG/0] OUT -----> Download go 1.9
   2017-10-24T14:03:19.69+0100 [STG/0] OUT -----> Download glide 0.13.0
   2017-10-24T14:03:23.85+0100 [STG/0] OUT -----> Download Nodejs 6.11.3
   2017-10-24T14:03:31.27+0100 [STG/0] OUT -----> Checking versions
   2017-10-24T14:03:31.28+0100 [STG/0] OUT ---------> Node Version: v6.11.3
   2017-10-24T14:03:31.56+0100 [STG/0] OUT ---------> NPM Version: 3.10.10
   2017-10-24T14:03:31.63+0100 [STG/0] OUT ---------> Go Version: go version go1.9 linux/amd64
   2017-10-24T14:03:31.78+0100 [STG/0] OUT ---------> Glide Version: glide version v0.13.0
   2017-10-24T14:03:31.78+0100 [STG/0] OUT Cache directory [/tmp/cache/final] exists
   2017-10-24T14:03:31.79+0100 [STG/0] OUT -----> Running stratos build compile [13:03:31]
   2017-10-24T14:03:31.79+0100 [STG/0] ERR /tmp/buildpackdownloads/652661b4b3c6701c6981e0b449bf726e/bin/compile: /tmp/app/deploy/cloud-foundry/build.sh: /bin/bash^M: bad interpreter: No such file or directory
   2017-10-24T14:03:31.79+0100 [STG/0] ERR Failed to compile droplet: Failed to compile droplet: exit status 126
   2017-10-24T14:03:31.81+0100 [STG/0] OUT Exit status 223
   2017-10-24T14:03:31.81+0100 [STG/0] ERR Staging failed: STG: Exited with status 223
   2017-10-24T14:03:31.81+0100 [STG/0] OUT Stopping instance 3012b34c-e599-4082-b42d-e29403e462cd
   2017-10-24T14:03:31.82+0100 [STG/0] OUT Destroying container
   2017-10-24T14:03:32.63+0100 [STG/0] OUT Successfully destroyed container

Fix is probably just to document making sure you use right Git settings.

Missing confirmation prompts for disruptive operations

Deployment type

(select the type below by replacing the space with an x)

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)

Expected behaviour

When I click potentially-disruptive commands (like "stop application" or "restart application") I get a confirmation prompt (similar to how clicking "terminate instance" pops up a confirmation prompt) before executing the command.

Actual behaviour

No confirmation prompt is shown and the command is executed immediately.

Steps to reproduce the behavior

Click on "stop application"
Notice that the application is stopped immediately with no confirmation prompt

Wrong information in UI for Disk and Memory usage of Application

Deployment type

Cloud Foundry Application (cf push)

Expected behaviour

cf app applog-firehose
Showing health and status for app applog-firehose in org PCFLogging / space applogs as admin...

name:              applog-firehose
requested state:   started
instances:         1/1
usage:             1G x 1 instances
routes:
last uploaded:     Fri 22 Sep 17:31:13 EDT 2017
stack:             cflinuxfs2
buildpack:         go_buildpack

     state     since                  cpu    memory        disk          details
#0   running   2017-11-21T04:59:04Z   1.6%   20.9M of 1G   78.3M of 1G

Actual behaviour

I'm getting wrong information of memory and disk usage in UI.

Could you please help us on this.
Appreciate your help.

Thanks,
Akhilesh Appana

Ease visibility of applications when on all orgs

It would be nice to easily determine app endpoint location when looking at all orgs/spaces. Applications may be named the same and they won't be visibly different.

Context

When deploying plenty of apps, if they are named equally, it would nice to determine which apps reside where while still looking at all applications

Clearly, this could be achieved by using the filter which is well implemented, but a color, tag or label would be nice to easily identify between environments, endpoints or even bare metal or cloud.

Possible Implementation

Watch warnings when running gulp dev

Deployment type

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
[x ] Other (please provide below)

Expected behaviour

Actual behaviour

I deployed the Back End & Now I'm developing the Front End in Local.
When running command gulp dev
I get these warnings. The application runs just fine though.

Steps to reproduce the behavior

Log output covering before error and any error statements

gulp dev
[10:08:23] Using gulpfile ~/stratos-ui/gulpfile.js
[10:08:23] Starting 'dev-build'...
[10:08:23] Starting 'clean'...
[10:08:24] Finished 'clean' after 1.43 s
[10:08:24] Starting 'prepare-frontend'...
[10:08:25] Finished 'prepare-frontend' after 494 ms
[10:08:25] Starting 'copy:configjs'...
[10:08:25] Starting 'copy:bowerjs'...
[10:08:25] Finished 'copy:configjs' after 72 ms
[10:08:25] Finished 'copy:bowerjs' after 60 ms
[10:08:25] Starting 'copy:js'...
[10:08:30] Finished 'copy:js' after 5.51 s
[10:08:30] Starting 'copy:lib'...
[10:08:31] Finished 'copy:lib' after 347 ms
[10:08:31] Starting 'css:generate'...
[10:08:32] Finished 'css:generate' after 1.74 s
[10:08:32] Starting 'css'...
[10:08:33] Finished 'css' after 866 ms
[10:08:33] Starting 'i18n'...
[10:08:33] Finished 'i18n' after 35 ms
[10:08:33] Starting 'dev-template-cache'...
[10:08:33] Finished 'dev-template-cache' after 2.96 ms
[10:08:33] Starting 'copy:html'...
[10:08:36] Finished 'copy:html' after 2.89 s
[10:08:36] Starting 'copy:assets'...
[10:08:36] Finished 'copy:assets' after 36 ms
[10:08:36] Starting 'i18n'...
[10:08:36] Starting 'copy:index'...
[10:08:36] Finished 'copy:index' after 9.83 ms
[10:08:36] Finished 'i18n' after 39 ms
[10:08:36] Starting 'inject:index'...
[10:08:37] gulp-inject 304 files into index.html.
[10:08:37] Finished 'inject:index' after 304 ms
[10:08:37] Finished 'dev-build' after 14 s
[10:08:37] Starting 'dev'...
[10:08:37] Starting 'browsersync'...
[10:08:37] Serving HTTPS with the default BrowserSync certificate
[10:08:37] Proxying API requests to: https://ows.cf.nd-paas.itn.ftgroup/pp
[10:08:37] Finished 'dev' after 294 ms
[Browsersync] Access URLs:
 --------------------------------------
       Local: https://localhost:3100
    External: https://10.194.9.216:3100
 --------------------------------------
          UI: http://localhost:3001
 UI External: http://10.194.9.216:3001
 --------------------------------------
[Browsersync] Serving files from: ./bower_components
[Browsersync] Serving files from: ./dist
[10:08:37] Finished 'browsersync' after 363 ms
[10:08:37] Starting 'watch'...
[10:08:37] 'watch' errored after 232 ms
[10:08:37] Error: watch /home/qdmb9595/stratos-ui/components/suse-branding/assets/images/ ENOSPC
    at exports._errnoException (util.js:1020:11)
    at FSWatcher.start (fs.js:1443:19)
    at Object.fs.watch (fs.js:1470:11)
    at Gaze._watchDir (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:289:30)
    at /home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:358:10
    at iterate (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/helper.js:52:5)
    at Object.forEachSeries (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/helper.js:66:3)
    at Gaze._initWatched (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:354:10)
    at Gaze.add (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:177:8)
    at new Gaze (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:74:10)
[10:08:37] Error in plugin 'run-sequence(watch)'
Message:
    watch /home/qdmb9595/stratos-ui/components/suse-branding/assets/images/ ENOSPC
Details:
    code: ENOSPC
    errno: ENOSPC
    syscall: watch /home/qdmb9595/stratos-ui/components/suse-branding/assets/images/
    filename: /home/qdmb9595/stratos-ui/components/suse-branding/assets/images/
Stack:
Error: watch /home/qdmb9595/stratos-ui/components/suse-branding/assets/images/ ENOSPC
    at exports._errnoException (util.js:1020:11)
    at FSWatcher.start (fs.js:1443:19)
    at Object.fs.watch (fs.js:1470:11)
    at Gaze._watchDir (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:289:30)
    at /home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:358:10
    at iterate (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/helper.js:52:5)
    at Object.forEachSeries (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/helper.js:66:3)
    at Gaze._initWatched (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:354:10)
    at Gaze.add (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:177:8)
    at new Gaze (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:74:10)

[12:27:17] GET      /v1/auth/session/verify```

1st class support for service plan & service instance

Actual behavior

The current UI requires the user to choose an application in order to access the services marketplace. This raises the following issues:

The user needs an application to access the services marketplace.
A simple display of the services marketplace requires the user to 1st browse through an application.
Service keys concept is not supported.

Expected/suggested behaviour

Add a 1st class support for service instances within a space.
Add a 1st class support for service plans (service offering in the market place) at the org and space level ( org-level service plan access and space-scoped brokers)

Such 1st class support might benefit from associated navigation flow in the side bar

/CC @gberche-orange

Deploy log: Investigate duplicate lines issue

From @irfanhabib on January 30, 2018 11:42

30/01/2018 11:41:40 AM: �[0;32m[INFO]	�[m--> Setting version for github.com/elgs/gostrgen to 9d61ae07eeaeb54ce2100022b1fd3ea020093d09.
30/01/2018 11:41:40 AM: �[0;32m[INFO]	�[mExporting resolved dependencies...
30/01/2018 11:41:40 AM: �[0;32m[INFO]	�[m--> Exporting github.com/elgs/gostrgen
30/01/2018 11:41:40 AM: �[0;32m[INFO]	�[m--> Setting version for github.com/elgs/gostrgen to 9d61ae07eeaeb54ce2100022b1fd3ea020093d09.
30/01/2018 11:41:40 AM: �[0;32m[INFO]	�[mExporting resolved dependencies...
30/01/2018 11:41:40 AM: �[0;32m[INFO]	�[m--> Exporting github.com/elgs/gostrgen
30/01/2018 11:41:40 AM: �[0;32m[INFO]	�[mReplacing existing vendor dependencies
30/01/2018 11:41:40 AM: �[0;32m[INFO]	�[mReplacing existing vendor dependencies
30/01/2018 11:41:40 AM: �[31;1m**WARNING**�[0m Installing package '.' (default)
30/01/2018 11:41:40 AM: -----> Running: go install -tags cloudfoundry -buildmode pie .
30/01/2018 11:41:40 AM: �[31;1m**WARNING**�[0m Installing package '.' (default)
30/01/2018 11:41:40 AM: -----> Running: go install -tags cloudfoundry -buildmode pie .
30/01/2018 11:41:51 AM: # github.com/irfanhabib/go-env
30/01/2018 11:41:51 AM: warning: unable to find runtime/cgo.a
30/01/2018 11:41:51 AM: # github.com/irfanhabib/go-env
30/01/2018 11:41:51 AM: warning: unable to find runtime/cgo.a
30/01/2018 11:41:52 AM: Exit status 0
30/01/2018 11:41:52 AM: Staging complete
30/01/2018 11:41:52 AM: Uploading droplet, build artifacts cache...
30/01/2018 11:41:52 AM: Uploading build artifacts cache...
30/01/2018 11:41:52 AM: Uploading droplet...
30/01/2018 11:41:52 AM: Exit status 0
30/01/2018 11:41:52 AM: Staging complete
30/01/2018 11:41:52 AM: Uploading droplet, build artifacts cache...
30/01/2018 11:41:52 AM: Uploading build artifacts cache...
30/01/2018 11:41:52 AM: Uploading droplet...
30/01/2018 11:41:53 AM: Uploaded build artifacts cache (197B)
30/01/2018 11:41:53 AM: Uploaded build artifacts cache (197B)
30/01/2018 11:41:56 AM: Uploaded droplet (705.3K)
30/01/2018 11:41:56 AM: Uploading complete
30/01/2018 11:41:56 AM: Uploaded droplet (705.3K)
30/01/2018 11:41:56 AM: Uploading complete
30/01/2018 11:41:58 AM: Destroying container
30/01/2018 11:41:58 AM: Destroying container
30/01/2018 11:41:59 AM: Successfully destroyed container
30/01/2018 11:41:59 AM: Successfully destroyed container
30/01/2018 11:42:11 AM:
30/01/2018 11:42:14 AM: 1 of 1 instances running
30/01/2018 11:42:14 AM: App started
30/01/2018 11:42:14 AM:
30/01/2018 11:42:14 AM: OK
30/01/2018 11:42:15 AM: App go-env-st2 was started using this command `go-env`
30/01/2018 11:42:15 AM: Showing health and status for app go-env-st2 in org e2e / space e2e as admin...
30/01/2018 11:42:20 AM: OK
30/01/2018 11:42:20 AM: requested state: started
30/01/2018 11:42:20 AM: instances: 1/1
30/01/2018 11:42:20 AM: usage: 16M x 1 instances
30/01/2018 11:42:20 AM: urls:
30/01/2018 11:42:20 AM: last uploaded: Tue Jan 30 11:42:11 UTC 2018
30/01/2018 11:42:21 AM: stack: cflinuxfs2
30/01/2018 11:42:21 AM: buildpack: Go
30/01/2018 11:42:21 AM: state since cpu memory disk details #0 running 2018-01-30 11:43:16 AM 0.0% 5.4M of 16M 2.6M of 16M```

_Copied from original issue: SUSE/stratos#199_

Deploy application: Override manifest fields

Allow the user to override certain manifest fields. This will allow, for example, deploying an app using the same repo multiple times by overriding the manifest name.

Step 1 - Allow user to override fields exposed by the push command
Step 2 - Allow user to override any manifest fields by updating the manifest used

schema isn't initializing

Deployment type

[X ] Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)

Expected behavior

console starts

Actual behavior

stratos is expecting a database but it isn't initializing

http://paste.opensuse.org/83806160

Steps to reproduce the behavior

cf create-service mysql-dev 20mb console_db -t stratos_mysql
cf push the stratos-ui

Log output covering before error and any error statements

2017-10-17T14:56:19.36-0500 [APP/PROC/WEB/0] OUT WARN[Tue Oct 17 19:56:19 UTC 2017] It appears schema isn't initialised yet, sleeping and trying again Exception occurred when fetching row count: Error 1146: Table 'cf_c0d6ed41_f3e9_49f5_b577_7cdeba27ce84.console_config' doesn't exist

application services using hard coded value for # of attachments

In src/plugins/cloud-foundry/view/applications/application/services/services.html we are using a hard coded value for services attached. Using this bug to track this so we can remember to fix later.

**1** Attached

Offline buildpacks

Deployment type

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
[x ] Other (please provide below)

Is there a support for Packaging Dependencies for Offline Buildpacks? If not, are you planning to do it in the future ? Any information you can provide me would be greatly appreciated, thank you.

Expected behaviour

Actual behaviour

Steps to reproduce the behavior

Log output covering before error and any error statements

Insert log here

User should be redirected to last accessed page

Currently, the user is always redirected to the "Workspaces" view on refresh even though they were looking at another page.

Marked potential security vulnerabilities

Deployment type

(select the type below by replacing the space with an x)

[] Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, using docker compose
Docker, single container deploying all components
Other (please provide below)

Apparently updating Marked to the latest release ^0.3.9 fixes the XSS vulnerabilities.

Expected behaviour

Actual behaviour

Steps to reproduce the behavior

Log output covering before error and any error statements

Insert log here