December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-422) File upload/manipulation through management API - modules, config files

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-422?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1396 to WFCORE-422: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-422 (was: WFLY-1396) Component/s: CLI (was: CLI) > File upload/manipulation through management API - modules, config files > ----------------------------------------------------------------------- > > Key: WFCORE-422 > URL: https://issues.jboss.org/browse/WFCORE-422 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Ondrej Zizka > > It would be nice to have a possibility to upload certain files. Namely: > - create modules (e.g. JDBC drivers) > - copy .properties files - logging, security etc. > - ssh keys, certificates etc. > Could be limited to the examples above - i.e. one operation for creating/removing a module, another for copying a file to configuration/ . > {code} > /:add-config-file(file=foo.properties, ifExists=fail|skip|overwrite|...) > /:add-module(file=foo.jar, name=org.jboss.foo, version=main, dependencies=["org.jboss.bar"], imports=[...] exports=[...] ifExists=fail|skip|overwrite|...) > {code} > To avoid the complexity of distributing such file amongst managed domain, the op could be scoped to just a single host, like > {code} > /host=host1:add-config-file(...) > {code} > File transfer > ============= > The same principle could be used as for deployments (--{{ModelNode.readExternal()}}-- ?) > CLI's DeployHander#execute(): > {code} > OperationBuilder op = new OperationBuilder(request); > op.addFileAsAttachment(f); > request.get(Util.CONTENT).get(0).get(Util.INPUT_STREAM_INDEX).set(0); > Operation operation = op.build(); > result = ctx.getModelControllerClient().execute(operation); > operation.close(); > {code} > Specifics > ========= > The file manipulation in add-module would be performed by JBoss Modules through an appropriate API. > The file manipulation in add-config-file would be performed by the part of AS which knows where the config is actually read from (in case it is variable) - MSC? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-423) No way to grep/more or find a line in the CLI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-423?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1123 to WFCORE-423: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-423 (was: WFLY-1123) Component/s: CLI (was: CLI) > No way to grep/more or find a line in the CLI > --------------------------------------------- > > Key: WFCORE-423 > URL: https://issues.jboss.org/browse/WFCORE-423 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jim Tyrrell > Assignee: Alexey Loubyansky > Labels: eap6-ux > > In the CLI I should be able to page through the pages of information that are presenting using | more or equivalent. By the same token I should be able to grep to find the one line that I am looking for, when I know what it is I am looking for. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-417) jboss-cli should set -Djava.awt.headless=true

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-417?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-2144 to WFCORE-417: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-417 (was: WFLY-2144) Component/s: CLI (was: CLI) > jboss-cli should set -Djava.awt.headless=true > --------------------------------------------- > > Key: WFCORE-417 > URL: https://issues.jboss.org/browse/WFCORE-417 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Robin Rosenberg > Assignee: Alexey Loubyansky > Priority: Minor > > On OS X using jboss-cli.sh will cause focus to shift making it very inconvenient to do other things while scripts that talk to jboss execute. > There is a workaround: export JAVA_OPTS=-Djava.awt.headless=true before invoking the cli, but I see no reason for the CLI not do this itself. This also applied to the adduser.sh script. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-418) Input/Output Formats Should Be Standard Formats (json/yaml/etc)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-418?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3339 to WFCORE-418: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-418 (was: WFLY-3339) Affects Version/s: (was: JBoss AS7 7.1.1.Final) Component/s: CLI (was: CLI) > Input/Output Formats Should Be Standard Formats (json/yaml/etc) > --------------------------------------------------------------- > > Key: WFCORE-418 > URL: https://issues.jboss.org/browse/WFCORE-418 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Environment: RHEL 6.4, x86_64 > Reporter: Chris Pitman > Assignee: Alexey Loubyansky > Labels: automation, cli, configuration_management, json > > The purpose of the CLI is to improve automation for administrators, but the format used for data is a non-standard format that cannot be easily parsed or generated by any language. > The format is *really* close to json, but with enough deviation to make munging it a pain: replace hash rockets (=>) with colons, undefined with null, and key value pairs ("(a => b)") with hashes ("{a : b}"). Going in the opposite direction requires some sort of cleverness to determine what is a key-value pair, which is not fun. > The CLI should support both output and input in a standard format, so that the above hoops do not have to be jumped through. > Steps to Reproduce: > 1. Connect to the jboss cli > 2. Execute "/:whoami" > Actual results: > { > "outcome" => "success", > "result" => {"identity" => { > "username" => "$local", > "realm" => "ManagementRealm" > }}, > "response-headers" => {"process-state" => "reload-required"} > } > Expected results: > { > "outcome": "success", > "result": {"identity": { > "username": "$local", > "realm": "ManagementRealm" > }}, > "response-headers": {"process-state": "reload-required"} > } -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-419) Expose client socket binding config through CLI connect configs

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-419?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-211 to WFCORE-419: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-419 (was: WFLY-211) Component/s: CLI (was: CLI) Fix Version/s: 1.0.0.Beta1 (was: 9.0.0.Beta1) > Expose client socket binding config through CLI connect configs > --------------------------------------------------------------- > > Key: WFCORE-419 > URL: https://issues.jboss.org/browse/WFCORE-419 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Brian Stansberry > Assignee: Alexey Loubyansky > Fix For: 1.0.0.Beta1 > > > Once AS7-6277 is done, continue exposing the client bind socket config to CLI users. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-420) Escape to shell

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-420?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-728 to WFCORE-420: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-420 (was: WFLY-728) Component/s: CLI (was: CLI) Fix Version/s: (was: No Release) > Escape to shell > --------------- > > Key: WFCORE-420 > URL: https://issues.jboss.org/browse/WFCORE-420 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Environment: all > Reporter: Rich Sharples > Assignee: Alexey Loubyansky > Priority: Minor > > It would be really useful to be able to escape to an (OS) shell from the CLI - most Linux commands / shells allow you to do this with eg. "!". -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-414) Issue in Interactive mode on cygwin not working.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-414?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-908 to WFCORE-414: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-414 (was: WFLY-908) Affects Version/s: (was: 8.0.0.CR1) Component/s: CLI (was: CLI) > Issue in Interactive mode on cygwin not working. > ------------------------------------------------ > > Key: WFCORE-414 > URL: https://issues.jboss.org/browse/WFCORE-414 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: Windows 7, windows2k8, Cygwin 1.7.15 > Reporter: Peter Cadman > Assignee: Alexey Loubyansky > Priority: Minor > > After connecting to standalone server on localhost, Cgywin doesn't response to input. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-415) Pressing up-arrow crashed CLI on windows

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-415?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1799 to WFCORE-415: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-415 (was: WFLY-1799) Affects Version/s: (was: 8.0.0.Alpha4) Component/s: CLI (was: CLI) > Pressing up-arrow crashed CLI on windows > ---------------------------------------- > > Key: WFCORE-415 > URL: https://issues.jboss.org/browse/WFCORE-415 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Nicklas Karlsson > Assignee: Alexey Loubyansky > > Pressing the up-arrow in the CLI on windows crashes it with > {code} > [standalone@localhost:9990 /] java.lang.NumberFormatException: For input string: > "1B" > at java.lang.NumberFormatException.forInputString(NumberFormatException. > java:65) > at java.lang.Integer.parseInt(Integer.java:492) > at java.lang.Integer.<init>(Integer.java:677) > at org.fusesource.jansi.AnsiOutputStream.write(AnsiOutputStream.java:120 > ) > at java.io.FilterOutputStream.write(FilterOutputStream.java:125) > at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) > at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) > at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295) > at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) > at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) > at java.io.PrintWriter.flush(PrintWriter.java:320) > at org.jboss.aesh.terminal.WindowsTerminal.writeToStdOut(WindowsTerminal > .java:88) > at org.jboss.aesh.console.Console.drawLine(Console.java:1011) > at org.jboss.aesh.console.Console.redrawLine(Console.java:990) > at org.jboss.aesh.console.Console.getHistoryElement(Console.java:753) > at org.jboss.aesh.console.Console.parseOperation(Console.java:556) > at org.jboss.aesh.console.Console.read(Console.java:446) > at org.jboss.aesh.console.Console.read(Console.java:346) > at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:177) > at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl. > java:1198) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:270) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:411) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-416) Inconsistent tab completion behaviour between commands and arguments

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-416?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-932 to WFCORE-416: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-416 (was: WFLY-932) Component/s: CLI (was: CLI) > Inconsistent tab completion behaviour between commands and arguments > -------------------------------------------------------------------- > > Key: WFCORE-416 > URL: https://issues.jboss.org/browse/WFCORE-416 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > > When tab is used for completion, the behavior changes when there is only 1 remaining candidate. > For commands, when the completion leads to a single candidate, a whitespace is appended and we can proceed to the arguments > For arguments using a TabCompleter, when the completion leads to a single candidate, no whitespace is appended and we have to type it to be able to proceed to the next argument > > Example: > * deployment-over<TAB> > => will complete to deployment-overlay<WHITESPACE><CURSOR> (a whitespace is appended to the single candidate) > * deployment-overlay a<TAB> > => will complete to deployment-overlay add<CURSOR> (no whitespace appended even though add is the only candidate matched) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-412) Pressing the tab key whilst entering a username for authentication deadlocks the CLI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-412?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3476 to WFCORE-412: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-412 (was: WFLY-3476) Affects Version/s: (was: 8.1.0.Final) Component/s: CLI (was: CLI) > Pressing the tab key whilst entering a username for authentication deadlocks the CLI > ------------------------------------------------------------------------------------ > > Key: WFCORE-412 > URL: https://issues.jboss.org/browse/WFCORE-412 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Darran Lofthouse > Assignee: Alexey Loubyansky > Attachments: cli_deadlock.txt > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014