Giter Club home page Giter Club logo

ui's Introduction

OpenTOSCA UI 2.0

Build Status License License

Part of the OpenTOSCA Ecosystem

Prerequisites

  1. Install Git
  2. Install and setup Node.js > 8.9 and NPM > 7.0 for Angular.io
  3. Install angular-cli npm install -g @angular/cli

Local Development Setup

  1. git clone https://github.com/OpenTOSCA/ui.git opentosca-ui && cd opentosca-ui
  2. npm install

Run Development Server

Run ng serve (or npm run start) for a dev server. Navigate to http://localhost:4202/. The app will automatically reload if you change any of the source files.

Note: Be sure that no other process is listening on port 4202. You can change the port in the defaults object in .angular-cli.json.

Production Build

Before conducting a release, we have to lock down the dependency versions:

npm install --no-shrinkwrap
npm shrinkwrap

Afterwards, run ng build (or npm run build) to build the project. The build artifacts will be stored in the dist/ directory. Use the -prod flag (or npm run build:prod) for a production build.

Lint the TypeScript project

ng lint

# or run
npm run lint

Build the WAR archive

mvnw clean package

Copy the WAR archive from Maven's build output directory (build\target) to your Apache Tomcat instance.

Code scaffolding

Use angular-cli to generate new files!

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|module.

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.

License

Copyright (c) 2016-2022 University of Stuttgart.

All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 and the Apache License v2.0 which both accompany this distribution, and are available at http://www.eclipse.org/legal/epl-v10.html and http://www.apache.org/licenses/LICENSE-2.0.

Haftungsausschluss

Dies ist ein Forschungsprototyp. Die Haftung für entgangenen Gewinn, Produktionsausfall, Betriebsunterbrechung, entgangene Nutzungen, Verlust von Daten und Informationen, Finanzierungsaufwendungen sowie sonstige Vermögens- und Folgeschäden ist, außer in Fällen von grober Fahrlässigkeit, Vorsatz und Personenschäden ausgeschlossen.

Disclaimer of Warranty

Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

ui's People

Contributors

buehlefs avatar dependabot[bot] avatar fakepk avatar kleinech avatar koppor avatar laviniastiliadou avatar lharzenetter avatar mar-be avatar mathonto avatar mee4895 avatar milesstoetzner avatar miwurster avatar nyuuyn avatar philwun avatar saatkamp avatar wederbn avatar zimmerml avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ui's Issues

Refresh in repository view changes repository URL back to default

Current Behavior:

If a user changes the repository URL, e.g., to http://<hostname>:8080/winery/servicetemplates and afterwards navigate to the Repository tab, the initial load of Service Templates works as expected. But, if the user presses the refresh button, the default repository URL is used (http://stable.winery.opentosca.org/servicetemplates) and not the configured one. Also, it seems the repository URL is somehow set back internally to the default value.

Expected Behavior:

The Repository tab should use the configured repository URL for the whole session.

Repository UI connection

Current Behavior:
The Repository API connection uses localhost as a default.

Expected Behavior:
Instead, it should use window.location per default. Similar to the Container API connection.

Steps to Reproduce:

  1. Open the UI with your machine's IP address
  2. Go to the administration tab

Other Information:
grafik

System Information:
OpenTOSCA Docker on Win10

Input parameters of passwords and private keys are visible in the UI

Current Behavior:
In some older version parameters which represented passwords (e.g. DBMSPassword) the input field hid the value (e.g. pw is shown as: ********).

Additionally, in older version if a parameter was a PrivateKey (e.g. VMPrivateKey) the input field didn't mess up the PrivateKey from a string perspective (e.g. the private key is broken and can't be used by some artefacts such as the SSH service for virtual machines)

Expected Behavior:
Password parameter values are hidden, PrivateKeys are still valid after pasting them into the field.

Steps to Reproduce:

  1. Use any CSAR (e.g. MyTinyTodo with MySQL) which has atleast one Password Parameter
  2. Use any CSAR which has a PrivateKey Input Parameter

Other Information:
Params not beeing hidden or well formatted:

screen shot 2018-03-19 at 14 51 39

Some logs when the private key is really needed:

screen shot 2018-03-19 at 14 51 18 2

P.S.: I know we can just escape the returns, but well, does it have to be done?! :P

System Information:
Mac OS X with Docker Setup and Chrome

Repository Management button

Current Behavior:
The Repository Managment button is pointing to the API (localhost:8080/winery/servicetemplates)

Expected Behavior:
The button should navigate the user to the repository UI (localhost:8080/#/servicetemplates).

Steps to Reproduce:

  1. Just click the button and you get a JSON response instead of the UI.

Other Information:

grafik

System Information:
OpenTOSCA Docker on Win10

Build Plan still running on DELETED Instance

Current Behavior:
screenshot from 2017-09-18 17-11-17

Expected Behavior:
Build plan should not be able to be running on a deleted Instance.

Steps to Reproduce:

  1. Create a new instance.
  2. Delete the instance while build plan is still running (or hung up because of an error).

Other Information:
Tested with the MyTinyToDoDockerContainer.csar

Broken file upload

Current Behavior:
It is not possible to use Firefox for csar uploading.

Expected Behavior:
It should set the file and the "Start Upload" button should appear.
Steps to Reproduce:

  1. Open UI with Firefox
  2. In the "Applications" tab select the "Upload new Application" button
  3. Use the "Select local File" button and try to upload a file

opentoscacsarupload

Other Information:
Error from terminal:
ERROR TypeError: n.srcElement is undefined Stack-Trace: cDNt/$l</n.prototype.onChange@http://192.168.0.20:8088/main.26cc8bffc54eb4f6f5b5.bundle.js:1:196285 hn/<@http://192.168.0.20:8088/main.26cc8bffc54eb4f6f5b5.bundle.js:1:83705 _@http://192.168.0.20:8088/vendor.40acdca35f6120df6524.bundle.js:1:40777 handleEvent@http://192.168.0.20:8088/vendor.40acdca35f6120df6524.bundle.js:1:48166 ie@http://192.168.0.20:8088/vendor.40acdca35f6120df6524.bundle.js:1:17241 je/<@http://192.168.0.20:8088/vendor.40acdca35f6120df6524.bundle.js:1:22858 v/<@http://192.168.0.20:8088/vendor.40acdca35f6120df6524.bundle.js:1:718813 eFQL/</</</l</e.prototype.invokeTask@http://192.168.0.20:8088/polyfills.043084ca495430fc14f3.bundle.js:1:41715 onInvokeTask@http://192.168.0.20:8088/vendor.40acdca35f6120df6524.bundle.js:1:11836 eFQL/</</</l</e.prototype.invokeTask@http://192.168.0.20:8088/polyfills.043084ca495430fc14f3.bundle.js:1:41628 eFQL/</</</u</r.prototype.runTask@http://192.168.0.20:8088/polyfills.043084ca495430fc14f3.bundle.js:1:36881 eFQL/</</</p</t.invokeTask@http://192.168.0.20:8088/polyfills.043084ca495430fc14f3.bundle.js:1:42853 h@http://192.168.0.20:8088/polyfills.043084ca495430fc14f3.bundle.js:1:22084 d@http://192.168.0.20:8088/polyfills.043084ca495430fc14f3.bundle.js:1:22304

System Information:
Tested on:
Windows 10 64Bit
Firefox 56.0 32Bit

TOSCA UI cannot render application detail page when Service template name is null

Current Behavior:

TOSCA UI cannot render application detail page when one of the Interface in the Service template name is null
User cannot click into detail for Application in TOSCA UI.
Expected Behavior:

user can clink into detail page regardless of interface name in service template but shows error/warning message
Steps to Reproduce:

  1. Upload a CSAR with a service template containing null interface name

ex.

  <Interface name="">
      <Operation name="OpenTOSCA-Lifecycle-Interface">
          <Plan planRef="MyTinyToDo_Bare_Docker_bpmn_buildPlan"/>
      </Operation>
  </Interface>

Other Information:

System Information:

Screen Shot 2022-03-08 at 16 23 27
Screen Shot 2022-03-10 at 12 03 55

[FR] Fading Notifications

Current Behavior:
Notification on the top right are never fading away

Expected Behavior:
Notification should fade away after some time

Steps to Reproduce:

  1. Upload a CSAR
  2. Watch the notification never leave

System Information:
Mac with OS X Sierra, tested with Docker-Compose and natively run version

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.