History

John Cowen c6db97b666 UI: Removes success notification on faking a success response for `self` (#4906 ) In order to continue supporting the legacy ACL system, we replace the 500 error from a non-existent `self` endpoint with a response of a `null` `AccessorID` - which makes sense (a null AccessorID means old API) We then redirect the user to the old ACL pages which then gives a 403 if their token was wrong which then redirects them back to the login page. Due to the multiple redirects and not wanting to test the validity of the token before redirecting (thus calling the same API endpoint twice), it is not straightforwards to turn the 'faked' response from the `self` endpoint into an error (flash messages are 'lost' through multiple redirects). In order to make this a slightly better experience, you can now return a `false` during execution of an action requiring success/failure feedback, this essentially skips the notification, so if the action is 'successful' but you don't want to show the notification, you can. This resolves showing a successful notification when the `self` endpoint response is faked. The last part of the puzzle is to make sure that the global 403 catching error in the application Route also produces an erroneous notification. Please note this can only happen with a ui client using the new ACL system when communicating with a cluster using the old ACL system, and only when you enter the wrong token. Lastly, further acceptance tests have been added around this This commit also adds functionality to avoid any possible double notification messages, to avoid UI overlapping		6 years ago
..
app	UI: Removes success notification on faking a success response for `self` (#4906 )	6 years ago
config	UI: Add conditional enterprise logo (#4432 )	6 years ago
lib	UI: New ACLs (#4789 )	6 years ago
public	…
tests	UI: Removes success notification on faking a success response for `self` (#4906 )	6 years ago
.dev.eslintrc.js	…
.editorconfig	…
.ember-cli	Move testing doubles to use data embedded in the HTML vs HTTP/fetch	6 years ago
.eslintrc.js	…
.gitignore	…
.nvmrc	…
.prettierrc	…
.watchmanconfig	…
GNUmakefile	Move testing doubles to use data embedded in the HTML vs HTTP/fetch	6 years ago
README.md	UI: New ACLs (#4789 )	6 years ago
ember-cli-build.js	ui: Adds multi syntax linting to the code editor (#4814 )	6 years ago
package.json	ui: Some trivial test additions, support env var passing of port numbers (#4728 )	6 years ago
testem.js	…
yarn.lock	UI: Removes success notification on faking a success response for `self` (#4906 )	6 years ago

README.md

consul-ui

Prerequisites

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

Installation

git clone https://github.com/hashicorp/consul.git this repository
cd ui-v2
yarn install

Running / Development

The source code comes with a small server that runs enough of the consul API as a set of mocks/fixtures to be able to run the UI without having to run consul.

make start-api or yarn start:api (this starts a Consul API double running on http://localhost:3000)
make start or yarn start to start the ember app that connects to the above API double
Visit your app at http://localhost:4200.

To enable ACLs using the mock API, use Web Inspector to set a cookie as follows:

CONSUL_ACLS_ENABLE=1

This will enable the ACLs login page, to which you can login with any ACL token/secret.

You can also use a number of other cookie key/values to set various things whilst developing the UI, such as (but not limited to):

CONSUL_SERVICE_COUNT=1000
CONSUL_NODE_CODE=1000
// etc etc

See ./node_modules/@hashicorp/consul-api-double for more details.

Code Generators

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

Running Tests

Please note: You do not need to run make start-api/yarn run start:api to run the tests, but the same mock consul API is used.

make test or yarn run test
make test-view or yarn run test:view to view the tests running in Chrome