June 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-452) Enhance s-ramp CLI property interpolation: support default values

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-452?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-452: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/437 > Enhance s-ramp CLI property interpolation: support default values > ------------------------------------------------------------------ > > Key: SRAMP-452 > URL: https://issues.jboss.org/browse/SRAMP-452 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Currently the shell supports property interpolation so that variables can be used in CLI command files. This takes the following form (for example): > {code} > connect http://localhost:8080/s-ramp ${username} ${password} > {code} > The CLI can then be invoked like this: > {code} > sramp.sh -f path/to/cli.txt -Dusername=admin -Dpassword=adminp > {code} > This is good, but let's also support optional default values for the variables, like this: > {code} > connect http://localhost:8080/s-ramp ${username:admin} ${password:adminp} > {code} > This will continue to replace ${username} with whatever value is passed via -Dusername=blah. However, if -Dusername is *not* provided, then the default value of 'admin' will be used. This will result in more powerful CLI scripts with commands like this: > {code} > connect ${sramp.endpoint:http://localhost:8080/s-ramp} ${sramp.username:admin} ${sramp.password:adminp} > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-451) S-ramp maven facade for fuse fabric

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-451?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-451: --------------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/436 > S-ramp maven facade for fuse fabric > ----------------------------------- > > Key: SRAMP-451 > URL: https://issues.jboss.org/browse/SRAMP-451 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Original Estimate: 1 week > Remaining Estimate: 1 week > > Create a mvn-http facade component that will act as a intermediate between fuse fabric and s-ramp.. It should be just a servlet that dissects the inbound request's path to extract the GAV information. Then does a s-ramp repository query to find the appropriate artifact > The GET side of that is very easy (pulling artifacts *from* s-ramp) > The servlet would have to take a URL path like this: org/overlord/sramp/s-ramp-api/0.4.0.Final/s-ramp-api-0.4.0.Final.jar and parse that to get the GAV info of: org.overlord.sramp:s-ramp-api:0.4.0.Final:jar -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-452) Enhance s-ramp CLI property interpolation: support default values

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-452?page=com.atlassian.jira.plugin.... ] Work on SRAMP-452 started by Eric Wittmann. > Enhance s-ramp CLI property interpolation: support default values > ------------------------------------------------------------------ > > Key: SRAMP-452 > URL: https://issues.jboss.org/browse/SRAMP-452 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Currently the shell supports property interpolation so that variables can be used in CLI command files. This takes the following form (for example): > {code} > connect http://localhost:8080/s-ramp ${username} ${password} > {code} > The CLI can then be invoked like this: > {code} > sramp.sh -f path/to/cli.txt -Dusername=admin -Dpassword=adminp > {code} > This is good, but let's also support optional default values for the variables, like this: > {code} > connect http://localhost:8080/s-ramp ${username:admin} ${password:adminp} > {code} > This will continue to replace ${username} with whatever value is passed via -Dusername=blah. However, if -Dusername is *not* provided, then the default value of 'admin' will be used. This will result in more powerful CLI scripts with commands like this: > {code} > connect ${sramp.endpoint:http://localhost:8080/s-ramp} ${sramp.username:admin} ${sramp.password:adminp} > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-454) CLI Command: Echo

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-454?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-454. ------------------------------- > CLI Command: Echo > ----------------- > > Key: SRAMP-454 > URL: https://issues.jboss.org/browse/SRAMP-454 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Implement a new CLI command that simply takes 1 argument (an arbitrary string) and echos it back. This would be helpful when running a CLI command file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-454) CLI Command: Echo

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-454?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-454. --------------------------------- Resolution: Done > CLI Command: Echo > ----------------- > > Key: SRAMP-454 > URL: https://issues.jboss.org/browse/SRAMP-454 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Implement a new CLI command that simply takes 1 argument (an arbitrary string) and echos it back. This would be helpful when running a CLI command file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-454) CLI Command: Echo

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-454?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-454: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/435 > CLI Command: Echo > ----------------- > > Key: SRAMP-454 > URL: https://issues.jboss.org/browse/SRAMP-454 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Implement a new CLI command that simply takes 1 argument (an arbitrary string) and echos it back. This would be helpful when running a CLI command file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-454) CLI Command: Echo

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-454?page=com.atlassian.jira.plugin.... ] Work on SRAMP-454 started by Eric Wittmann. > CLI Command: Echo > ----------------- > > Key: SRAMP-454 > URL: https://issues.jboss.org/browse/SRAMP-454 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Implement a new CLI command that simply takes 1 argument (an arbitrary string) and echos it back. This would be helpful when running a CLI command file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-454) CLI Command: Echo

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-454?page=com.atlassian.jira.plugin.... ] Eric Wittmann reassigned SRAMP-454: ----------------------------------- Assignee: Eric Wittmann (was: Brett Meyer) > CLI Command: Echo > ----------------- > > Key: SRAMP-454 > URL: https://issues.jboss.org/browse/SRAMP-454 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Implement a new CLI command that simply takes 1 argument (an arbitrary string) and echos it back. This would be helpful when running a CLI command file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-380) Passwords in clear text when running in Fuse 6.1

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-380?page=com.atlassian.jira.plugin.... ] Eric Wittmann reassigned SRAMP-380: ----------------------------------- Assignee: Eric Wittmann (was: Kurt Stam) > Passwords in clear text when running in Fuse 6.1 > ------------------------------------------------ > > Key: SRAMP-380 > URL: https://issues.jboss.org/browse/SRAMP-380 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > When we install into JBoss EAP we make sure that we don't have any clear text passwords in any configuration files. This is made possible by using the Vault, which allows us to store passwords in the vault and then refer to those vault locations from our config files. > I don't know if there is something similar to be done in Fuse 6.1 > In addition, the login credentials for supported users in EAP are not stored in clear text (the EAP Application Realm config files store an encrypted version of the passwords). > In Fuse 6.1 we are storing the login user credentials in a users.properties file in clear text. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-404) Create a Deriver for WADL files

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-404?page=com.atlassian.jira.plugin.... ] Eric Wittmann reassigned SRAMP-404: ----------------------------------- Assignee: Brett Meyer (was: Kurt Stam) > Create a Deriver for WADL files > ------------------------------- > > Key: SRAMP-404 > URL: https://issues.jboss.org/browse/SRAMP-404 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.5.0.Final > > > We currently have Derivers for WSDL and related SOA artifact types, but it would be nice to have a Deriver for WADL files. > This feature request initiated from: > https://community.jboss.org/message/869323 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2014