* Adding cluster menu colors
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Adding theme class name flag into #app
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Cleaning up mixins
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Tuning up Wizard Layout styles
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Using theme-light global flag
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Minor style fixes
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Using .theme-light flag across components
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Set theme as @computed value
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Preventing Drawer slide-in scroll flickering
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Setting background for settings views
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Minor layout fixes
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Switching AceEditor theme reactively
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* Cleaning up
Signed-off-by: Alex Andreev <alex.andreev.email@gmail.com>
* extract missing localizations from last master <- pr-merge
Signed-off-by: Roman <ixrock@gmail.com>
* fix: prevent app-crash in preferences in case of incorrect http-proxy value
Signed-off-by: Roman <ixrock@gmail.com>
* fix: don't repeat ipc-sync message to main renderer process/window when sending to frames
Signed-off-by: Roman <ixrock@gmail.com>
Signed-off-by: Roman <ixrock@gmail.com>
Co-authored-by: Sebastian Malton <sebastian@malton.name>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Lauri Nevala <lauri.nevala@gmail.com>
Co-authored-by: Alex Andreev <alex.andreev.email@gmail.com>
* Add support for customreasourcedefinitions under the v1 API
* moving store and views to use v1
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
* use the Kubernetes regex for matching system names
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
* adding port-forward for containers in pods
address review comments
use more idiomatic approach for async code
move some files in advance of merge conflict with Lens restructure work
* Separate the port forward links in the UI (so they don't all spin when one link is clicked)
* minor fixes
* addressed review comments (replaced <p> with <div>, moved key attribute to proper element)
* fix lint issue
* removed extraneous <div> from pod container port details
Signed-off-by: Jim Ehrismann <jehrismann@mirantis.com>
* add parsing of quota values which are non-numeric in the general case
* add unit tests
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
* fix format duration rounding days error
* added tests
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
Signed-off-by: Jussi Nummelin <jussi.nummelin@gmail.com>
Co-authored-by: Lauri Nevala <lauri.nevala@gmail.com>
Co-authored-by: Jari Kolehmainen <jari.kolehmainen@gmail.com>
* add LANG env with UTF-8 specified
* fix precedence of union of env objects
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
* fix parseApi not accepting versions that don't start with 'v'
* add unit tests
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
* fix parseApi not accepting versions that don't start with 'v'
Signed-off-by: Sebastian Malton <smalton@mirantis.com>
Co-authored-by: Sebastian Malton <smalton@mirantis.com>
* Let OS allocate port number
Port availability might be tricky if some port is already in use on the
'all' interface '0.0.0.0'.
The proposed solution is to let the OS allocate the port for us using 0
as port specifier :
- first create a server instance to allocate a port number
- save port number
- close the server
- return the port number to the caller
This should be safe granted the OS doesn't reuse the port numbers on
consecutive port allocations.
see :
- about Node.js Net module : https://nodejs.org/docs/latest-v12.x/api/net.html#net_server_listen_port_host_backlog_callback
- about safety around reusing port number : https://unix.stackexchange.com/a/132524
Signed-off-by: Alexis Deruelle <alexis.deruelle@gmail.com>
