kui-shell / kuiclienttemplate Goto Github PK

View Code? Open in Web Editor NEW

30.0 30.0 8.0 1.37 MB

Use this template to make your own custom graphical terminal, via the Kui Grahpical CLI Framework

Home Page: https://github.com/kubernetes-sigs/kui

TypeScript 95.25% SCSS 0.39% Shell 4.35%

electron krew krew-plugin kubectl kubectl-plugins kubernetes kui visualization

kuiclienttemplate's People

Contributors

Stargazers

Watchers

Forkers

myan9 mdheller csantanapr starpit tetrahedral joshmayberry micromouf

kuiclienttemplate's Issues

webpack-dev-server seems not to start correctly the second time

there seems to be some bug in webpack-dev-server. if you do

npm ci
npm run webpack

then visit localhost:9080... so far, so good. then if you ctrl-c that, and run npm run webpack again and visit localhost:9080, you will see errors. this time, webpack has generated code that has node_modules/node_modules/@kui-shell in its webpack-require generated code

re-running npm ci prior to the npm run webpack, and it's fine again. weird.

`k logs` doesn't take selector correctly

The following screenshot shows how k logs -l looks like in plugin-kubeui:

k logs is usually followed by entityName, but entityName is not required when selector is available. The logs handler doesn't handle with this use case.

The following screenshot shows the correct behavior in plain terminal:

bugs in contexts table

row clicks do not work

build:krew target uses undefined build target

it should be build:electron:all

bump to kui 5.2.4

this will pick up the needed API changes

bump to kui 5.4.1

several issues:

I tried to start proxy with KUBECONFIG, but sees not work

git clone https://github.com/kui-shell/plugin-kubeui && cd plugin-kubeui
npm ci
KUBECONFIG=xxxx npm run proxy &  
npm run webpack

The output is like below, seems the KUBECONFIG env variable is not there.

❯
ready
Successfully connected to your cloud. For next steps, try this command: getting started
❯
env
KUI=true
TERM=xterm-color
KUI_REPL_MODE=stdout
KUI_EXEC_OPTIONS={"noHistory":true,"rethrowErrors":true,"type":2,"env":{},"nested":true,"isProxied":true,"credentials":{},"rawResponse":true,"language":"en-US"}
__CF_USER_TEXT_ENCODING=0x1F5:0x19:0x34
PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin
LOCALE=en-US
DEVMODE=true
PWD=/
SHLVL=3
HOME=/Users/shenxh
KUI_HEADLESS=true
_=/usr/bin/env
❯
kubectl get pod
The connection to the server localhost:8080 was refused - did you specify the right host or port?

and the UI console has many error like

Not allowed to load local resource: file:///Applications/Utilities/Terminal.app/Contents/Resources/Fonts/SFMono-Light.otf

if I stop the npm run webpack and run again, when access http://localhost:9080, will show errors like below

clean dist and node-modules and rerun `npm ci` can resolve this issue.

enable webpack tests in travis

remove remaining uses of direct: API

clarify screenshot discussion in readme

it's unclear to which screenshot we refer

move Events to be a button

kui 5.2.29 has improved support for Buttons in multi modal responses. let's start by moving the Events tab to be a button, so that the events table (along with the associated get events command) show up in the REPL. then, clicks on that table can re-populate the sidecar with the chosen event resource

test

/kind test
/priority fun

clean up last-applied

the code is messy and makes unnecessary use of low-level apis: type: 'custom'

add screenshot to readme

bump to kui-core 5.4.2

bump to kui-core 5.4.4

this introduces some optimizations to startup time

add Job and isJob impls

export the doExecWith... functions

we should probably export doExecWithStdout, doExecWithPty, doExecWithStatus, and doExecWithTable to allow other plugins a higher level way to call kubectl.

they could always do a REPL.qexec, but if the goal of the separate plugin is to offer new kubectl listen or Mode enhancements (e.g. log formatting), rather than just consuming a kube resource model, those doExec routines do offer some assistance. (e.g., if the goal of that other plugin is do do something with a kube resource, or display a kube table, a qexec is probably fine, because this plugin has listen functions that export the needed information via qexec)

add krew manifest

krew: https://github.com/kubernetes-sigs/krew/

krew manifest docs: https://github.com/kubernetes-sigs/krew/blob/master/docs/DEVELOPER_GUIDE.md#writing-a-plugin-manifest

bump to kui 5.4.0

add isPod and isDeployment to public API

update to kui 5.2.21

release builds as github releases

on master tag builds, travis should release electron builds to github

allow resource providers to define their own Summary

right now, the Summary mode assumes that kubectl get <kind> works for that resource type. this is not always the case. we could allow resource providers to define their own Summary, for those cases

improve InvolvedObject handling

we can improve inter-object navigation by leveraging InvolvedObject

krew manifest has the wrong bin

missing .sh suffix

prebuilt image -> prebuilt images (in readme)

Auto completion for kubectl

Is it possible to add auto completion for kubectl?

update mode registration to new high-level API

in kui 5.2.19

bump to kui-core 5.4.3

tests!

get the tests working, and in travis

bump to kui 5.2.32

Code and Contribute does not work

[root@agentavtone-masterone ~]# git clone https://github.com/kui-shell/plugin-kubeui && cd plugin-kubeui
Cloning into 'plugin-kubeui'...
remote: Enumerating objects: 14, done.
remote: Counting objects: 100% (14/14), done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 759 (delta 0), reused 2 (delta 0), pack-reused 745
Receiving objects: 100% (759/759), 1.15 MiB | 13.20 MiB/s, done.
Resolving deltas: 100% (403/403), done.
[root@agentavtone-masterone plugin-kubeui]# ls
attic  docs         lerna.json    package-lock.json  README.md  tools
bin    kubeui.yaml  package.json  plugins            theme      tsconfig.json
[root@agentavtone-masterone plugin-kubeui]# npm ci

Usage: npm <command>

where <command> is one of:
    access, adduser, bin, bugs, c, cache, completion, config,
    ddp, dedupe, deprecate, dist-tag, docs, edit, explore, get,
    help, help-search, i, init, install, install-test, it, link,
    list, ln, login, logout, ls, outdated, owner, pack, ping,
    prefix, prune, publish, rb, rebuild, repo, restart, root,
    run, run-script, s, se, search, set, shrinkwrap, star,
    stars, start, stop, t, tag, team, test, tst, un, uninstall,
    unpublish, unstar, up, update, v, version, view, whoami

npm <cmd> -h     quick help on <cmd>
npm -l           display full usage info
npm help <term>  search for help on <term>
npm help npm     involved overview

Specify configs in the ini-formatted file:
    /root/.npmrc
or on the command line via: npm <command> --key value
Config info can be viewed via: npm help config

[email protected] /usr/lib/node_modules/npm
[root@agentavtone-masterone plugin-kubeui]#

enhance events display

enhance nameHash parsing to support the pattern used by events
add Show Involved Object mode button