History

Matthew Irish f38a50b6b2 UI - unauthed login methods (#4854 ) * fetch auth methods when going to the auth route and pass them to the auth form component * add boolean editType for form-fields * look in the data hash in the serializer * remove renderInPlace for info-tooltips as it does something goofy with widths * add new fields for auth methods * fix console refresh command on routes that use lazyPaginatedQuery * add wrapped_token param that logs you in via the token backend and show other backends if your list contains supported ones * handle casing when looking up supported backends * change listingVisibility to match the new API * move wrapped_token up to the vault route level so it works from the app root		2018-07-05 13:28:12 -05:00
..
app	UI - unauthed login methods (#4854 )	2018-07-05 13:28:12 -05:00
config	Ui kv preflight endpoints (#4439 )	2018-04-24 16:30:44 -05:00
lib	UI - upgrading generic secret engines to v2 format (#4750 )	2018-06-13 23:06:19 -05:00
mirage
public
scripts	UI - upgrading generic secret engines to v2 format (#4750 )	2018-06-13 23:06:19 -05:00
tests	UI - unauthed login methods (#4854 )	2018-07-05 13:28:12 -05:00
vendor
.editorconfig
.ember-cli
.eslintrc.js
.gitignore
.travis.yml
.watchmanconfig
ember-cli-build.js	UI ensure trailing slash (#4828 )	2018-06-25 15:30:11 -05:00
package.json	UI - guard page redesign (#4779 )	2018-06-26 16:35:47 -05:00
README.md	update the readme to be more useful for UI development (#4399 )	2018-04-19 16:08:41 -05:00
testem.js	Skip flakey UI test (#4762 )	2018-06-14 09:43:38 -04:00
yarn.lock	UI - guard page redesign (#4779 )	2018-06-26 16:35:47 -05: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.

Node.js (with NPM)
Bower
Yarn
Ember CLI

Running / Development

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

yarn && bower install

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

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.