History

Kenia 7c203a9220 ui: Create PopoverSelect, CatalogToolbar, and update tests (#7489 ) * Create PopoverSelect component and styling * Create CatalogToolbar component and Styling * ui: Adds `selectable-key-values` helper (#7472) Preferably we want all copy/text to live in the template. Whilst you can achieve what we've done here with a combination of different helpers, as we will be using this approach in various places it's probably best to make a helper. We also hit an ember bug related to using the `let` helper and trying to access `thingThatWasLet.firstObject` (which can also be worked around using `object-at`). Moving everything to a helper 'sorted' everything. Probably worthwhile noting that if the sort option themselves become dynamic, I'm not sure if the helper here would actually react as you would expect (I'm aware that ember helpers on react on the root arguments, not necesarily sub properties of those arguments). If we get to that point this helper could take the same approach as what I believe ember-composable-helpers does to get around this, or move them to the view controller. If we do ever moved this to the view controller, we can still use the exported function from the new helper here to keep using the same functionality and tests we have here. * Create tests for sorting services with CatalogToolbar * Add rule to print 'ember/no-global-jquery' as a warning Co-authored-by: John Cowen <johncowen@users.noreply.github.com>		2020-05-12 17:14:48 +00:00
..
app	ui: Create PopoverSelect, CatalogToolbar, and update tests (#7489 )	2020-05-12 17:14:48 +00:00
blueprints
config
lib
node-tests/config
public
tests	ui: Create PopoverSelect, CatalogToolbar, and update tests (#7489 )	2020-05-12 17:14:48 +00:00
.dev.eslintrc.js
.editorconfig
.ember-cli
.eslintignore
.eslintrc.js	ui: Create PopoverSelect, CatalogToolbar, and update tests (#7489 )	2020-05-12 17:14:48 +00:00
.gitignore
.istanbul.yml
.nvmrc
.prettierrc
.template-lintrc.js
.travis.yml
.watchmanconfig
_redirects
ember-cli-build.js	ui: Redesign - Service List page with Gateways (#7781 )	2020-05-12 17:14:42 +00:00
GNUmakefile
package.json	ui: Model Layer for SSO Support (#7771 )	2020-05-12 17:14:41 +00:00
README.md
testem.js
yarn.lock	ui: Redesign - Gateway Instances List page (#7796 )	2020-05-12 17:14:45 +00:00

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

All tooling scripts below primarily use make which in turn call node package scripts.

Running / Development

The source code comes with a small development mode 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 or yarn start to start the ember app
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.

If you wish to run the UI code against a running consul instance, uncomment the proxy line in .ember-cli to point ember-cli to your consul instance.

You can also run the UI against a normal Consul installation.

make start-consul or yarn run start:consul will use the CONSUL_HTTP_ADDR environment variable to locate the Consul installation. If that it not set start-consul will use http://localhost:8500.

Example usage:

CONSUL_HTTP_ADDR=http://10.0.0.1:8500 make start-consul

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

Linting

make lint currently runs linting on the majority of js files and hbs files (using ember-template-lint).

See .eslintrc.js and .eslintignore for specific configuration.

Building

make build builds the UI for production usage (env=production)
make build-ci builds the UI for CI/test usage (env=test)

Static files are built into ./dist

Running Tests in Parallel

Alternatively, ember-exam can be used to split the tests across multiple browser instances for faster results. Most options are the same as ember test. To see a full list of options, run ember exam --help.

Note: The EMBER_EXAM_PARALLEL environment variable must be set to override the default parallel value of 1 browser instance in testem.js.

To quickly run the tests across 4 parallel browser instances:

make test-parallel

To run manually:

$ EMBER_EXAM_PARALLEL=true ./node_modules/.bin/ember exam --split <num> --parallel

More ways to split tests can be found in the ember-exam README.md.