luxolus/open-vault
2
0
Fork 0
Code Issues 1 Pull requests Releases Activity
open-vault/ui
History
Matthew Irish 5ca987662f
UI - new token renew banner (#5662) 
* move warning banner out of token-expire-warning and into user menu
* check renewal status every 5s, and resume auto-renew if a user becomes active again
* use a link in the token-expire-warning
* add test for new expiration functionality
* fix license test
* use features helper in license test
* fix import
* use yarn 1.12.1
* remove mirage
* skip some tests for now
* use eslintignore
* logout after auth tests
* use new alert-banner for auth info warning
* add data-test selector back
* move identity back to a button, and style button.link
* make the warning message the right color
* fix shamir test
* review feedback
2018-11-05 10:56:59 -06:00
..
app UI - new token renew banner (#5662) 2018-11-05 10:56:59 -06:00
config Ember update (#5386) 2018-09-25 11:28:26 -05:00
lib UI - upgrading generic secret engines to v2 format (#4750) 2018-06-13 23:06:19 -05:00
public Ember update (#5386) 2018-09-25 11:28:26 -05:00
scripts UI - new token renew banner (#5662) 2018-11-05 10:56:59 -06:00
tests UI - new token renew banner (#5662) 2018-11-05 10:56:59 -06:00
vendor UI: ember-auto-import (#4933) 2018-07-18 09:13:39 -05:00
.editorconfig Ember update (#5386) 2018-09-25 11:28:26 -05:00
.ember-cli Moving UI assets to OSS 2018-04-03 09:16:57 -05:00
.eslintignore UI - new token renew banner (#5662) 2018-11-05 10:56:59 -06:00
.eslintrc.js ui: use prettier with eslint 2018-11-01 14:45:23 -07:00
.gitignore Ember update (#5386) 2018-09-25 11:28:26 -05:00
.prettierrc ui: use prettier with eslint 2018-11-01 14:45:23 -07:00
.template-lintrc.js Ember update (#5386) 2018-09-25 11:28:26 -05:00
.watchmanconfig Moving UI assets to OSS 2018-04-03 09:16:57 -05:00
ember-cli-build.js Ember update (#5386) 2018-09-25 11:28:26 -05:00
package.json UI - new token renew banner (#5662) 2018-11-05 10:56:59 -06:00
README.md docs: add note about husky and lint-staged 2018-11-01 14:45:25 -07:00
testem.js Ember update (#5386) 2018-09-25 11:28:26 -05:00
yarn.lock UI - new token renew banner (#5662) 2018-11-05 10:56:59 -06:00

README.md

vault

This README outlines the details of collaborating on this Ember application. A short introduction of this app could easily go here.

Prerequisites

You will need the following things properly installed on your computer.

*You will need to install Husky and lint-staged locally by running npm install husky lint-staged. However please note these dependencies cannot be added to the package.json to ensure that husky doesn't run on commits unrelated to the Vault UI.

Running / Development

To get all of the JavaScript dependencies installed, run this in the ui directory:

yarn

If you want to run Vault UI and proxy back to a Vault server running on the default port, 8200, run the following in the ui directory:

  • yarn run start

This will start an Ember CLI server that proxies requests to port 8200, and enable live rebuilding of the application as you change the UI application code. Visit your app at http://localhost:4200.

If your Vault server is running on a different port you can use the long-form version of the npm script:

ember server --proxy=http://localhost:PORT

Code Generators

Make use of the many generators for code, try ember help generate for more details

Running Tests

Running tests will spin up a Vault dev server on port 9200 via a pretest script that testem (the test runner) executes. All of the acceptance tests then run, proxing requests back to that server.

  • yarn run test-oss
  • yarn run test-oss -s to keep the test server running after the initial run.
  • yarn run test -f="policies" to filter the tests that are run. -f gets passed into QUnit's filter config

Linting

  • yarn lint:hbs
  • yarn lint:js
  • yarn lint:js -- --fix

Building Vault UI into a Vault Binary

We use go-bindata-assetfs to build the static assets of the Ember application into a Vault binary.

This can be done by running these commands from the root directory run: make static-dist make dev-ui

This will result in a Vault binary that has the UI built-in - though in a non-dev setup it will still need to be enabled via the ui config or setting VAULT_UI environment variable.

Further Reading / Useful Links