NETOBSERV-316 Console plugin as standalone

[jpinsonneau]

This allow to run plugin as standalone. You can port-forward loki from anywhere or mock it.

Simply run make start-standalone to run backend + standalone frontend with live reloading
Or build-standalone then make serve.

Generated index.html + js files are hosted in backend at http://localhost:9001/

You can run cypress testing using this method. Simply update port number in consts.js

Will need #152 to support dark theme & implements ResourceLink icons. This can be added in another PR.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[OlivierCazade]

/lgtm

I just had to run install-frontend before start-standalone to make it work.
Thanks!

[jpinsonneau]

I just had to run install-frontend before start-standalone to make it work. Thanks!

Yes I can add this on both start / start-standalone 👍
Thanks for the feedback @OlivierCazade

[OlivierCazade]

/lgtm

[eranra]

@jpinsonneau just ran that on my machine ... looks good to me. some remarks::

(1) the term install in the Makefile is a bit confusing ... it might be better to use something like deploy or/and build those terms are easier to understand and not ambiguous.

(2) For completeness, it might be nice to have some mock Loki (or simulation) of data so that when you run the plug-in without real data we will be able to show something.

(3) From looking on the screenshot - need to add the nice icons back :-)

[jpinsonneau]

(1) the term install in the Makefile is a bit confusing ... it might be better to use something like deploy or/and build those terms are easier to understand and not ambiguous.

This actually come from npm install. We can add dependencies keyword as same as in the echo command or maybe npm mention ?

.PHONY: install-frontend
install-frontend:
	@echo "### Installing frontend dependencies"
	cd web && npm ${NPM_INSTALL}

Or remove these and run npm install directly. What would you prefer ?

(2) For completeness, it might be nice to have some mock Loki (or simulation) of data so that when you run the plug-in without real data we will be able to show something.

I'm on it 👍 currently we have the json-server but the jsons are outdated. I'm also looking if we can have something better like reusing mocks from tests or restore a loki storage from previous saved data.

(3) From looking on the screenshot - need to add the nice icons back :-)

This will be done after #152 merge

Thanks for the feedback @eranra !

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from eranra after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jpinsonneau]

Rebased and added missing resource icons:

It seems there are issues with button styles in dark 🤔 The PF colors are not dynamically updating on theme change and I can't find a workaround for now.

[jpinsonneau]

Rebased to test with cypress and fixed lasts styling issues
Also added start-standalone-mock to run standalone with mocked loki backend