7bf3476be9
* remove unused response-wrapping route and controller
* move to using the internal mounts endpoint for the secrets list and individual engine lookup
* remove errors about sys/mounts access because we don't need it anymore 🎉
* use modelFor instead of peekRecord for looking up the secret-engine
* remove test because we removed that error page - in the worst case scenario, a user will only have access to cubbyhole, but will see that in the secrets engines list
* make the dev CSP the same as the Go CSP
* update serializer to handle SSH responses as well as new engine fetches
* back out some changes to ttl-picker and field test object so that tests pass
* get rid of trailing space in the secret engine link
* add secrets-engine adapater tests for new query behavior
|
||
|---|---|---|
| .. | ||
| app | ||
| config | ||
| lib | ||
| mirage | ||
| public | ||
| scripts | ||
| tests | ||
| vendor | ||
| .bowerrc | ||
| .editorconfig | ||
| .ember-cli | ||
| .eslintrc.js | ||
| .gitignore | ||
| .travis.yml | ||
| .watchmanconfig | ||
| bower.json | ||
| ember-cli-build.js | ||
| package.json | ||
| README.md | ||
| testem.js | ||
| yarn.lock | ||
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.
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-ossyarn run test-oss -sto keep the test server running after the initial run.yarn run test -f="policies"to filter the tests that are run.-fgets passed into QUnit'sfilterconfig
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.