[JBoss JIRA] (SRAMP-573) Ctrl+C should not exit the CLI
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-573:
---------------------------------
Summary: Ctrl+C should not exit the CLI
Key: SRAMP-573
URL: https://issues.jboss.org/browse/SRAMP-573
Project: S-RAMP
Issue Type: Bug
Reporter: Brett Meyer
Assignee: David virgil naranjo
If you mistype a command in the CLI, I'd expect Ctrl+C to clear it. Instead, it exits the shell completely. Instead, limit that to Ctrl+D. Block Ctrl+C from exiting and ensure it clears the current partially-typed command.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (SRAMP-571) Support stored queries in UI
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-571:
---------------------------------
Summary: Support stored queries in UI
Key: SRAMP-571
URL: https://issues.jboss.org/browse/SRAMP-571
Project: S-RAMP
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
SRAMP-29 added support for stored queries. Once SRAMP-554 is finished, add stored query support in the UI. Consider adding a "Save as Stored Query" button to the search sidebar or above the search results. The latter may be more natural. When clicked, it would open a small prompt to provide a name.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (RTGOV-510) Situation state transition to Close causes resolutionState and assignedTo properties to be cleared
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-510?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-510:
----------------------------------
[~michaelclay] Could you confirm whether you are happy for the 'resolutionState' and 'assignedTo' properties to remain set when moved to closed state?
> Situation state transition to Close causes resolutionState and assignedTo properties to be cleared
> --------------------------------------------------------------------------------------------------
>
> Key: RTGOV-510
> URL: https://issues.jboss.org/browse/RTGOV-510
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Components: User Interface
> Reporter: Gary Brown
> Assignee: Michael Clay
> Fix For: 2.0.0.Final
>
>
> Currently when transitioning a Situation to the Closed state causes the 'resolutionState' and 'assignedTo' properties to be cleared.
> This is the same state as when the Situation is first created and therefore creates an ambiguity regarding whether the situation has been dealt with.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (SRAMP-570) Improve s-ramp commands for Fuse/Fabric
by David virgil naranjo (JIRA)
[ https://issues.jboss.org/browse/SRAMP-570?page=com.atlassian.jira.plugin.... ]
David virgil naranjo commented on SRAMP-570:
--------------------------------------------
That's good! Thanks!
> Improve s-ramp commands for Fuse/Fabric
> ---------------------------------------
>
> Key: SRAMP-570
> URL: https://issues.jboss.org/browse/SRAMP-570
> Project: S-RAMP
> Issue Type: Enhancement
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> For Fuse:
> 1.) Make the password argument optional
> 2.) If no Overlord installation has been attempted (the existence of overlord.properties in FUSE/etc is a good test), fail if no password is provided
> 3.) If a password is provided, but overlord.properties already exists, print what Gary mentioned: an installation already exists, re-using those credentials, but the "overlord:changePassword" command is available
> 4.) Create overlord:changePassword. It would regenerate the keystore and update any applicable *.properties values
> Modify/Add commands to deploy in Fuse Fabric. Create new commands. They would be like fuse commands, but starting by fabric : fabric:overlord:s-ramp:configure
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (SRAMP-570) Improve s-ramp commands for Fuse/Fabric
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-570?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-570:
-----------------------------------
If that's the case, then sure. But +1 on Gary's suggestion: use something like overlord:s-ramp:configureFabric (keep "overlord" as the leading namespace)
> Improve s-ramp commands for Fuse/Fabric
> ---------------------------------------
>
> Key: SRAMP-570
> URL: https://issues.jboss.org/browse/SRAMP-570
> Project: S-RAMP
> Issue Type: Enhancement
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> For Fuse:
> 1.) Make the password argument optional
> 2.) If no Overlord installation has been attempted (the existence of overlord.properties in FUSE/etc is a good test), fail if no password is provided
> 3.) If a password is provided, but overlord.properties already exists, print what Gary mentioned: an installation already exists, re-using those credentials, but the "overlord:changePassword" command is available
> 4.) Create overlord:changePassword. It would regenerate the keystore and update any applicable *.properties values
> Modify/Add commands to deploy in Fuse Fabric. Create new commands. They would be like fuse commands, but starting by fabric : fabric:overlord:s-ramp:configure
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (SRAMP-570) Improve s-ramp commands for Fuse/Fabric
by David virgil naranjo (JIRA)
[ https://issues.jboss.org/browse/SRAMP-570?page=com.atlassian.jira.plugin.... ]
David virgil naranjo commented on SRAMP-570:
--------------------------------------------
But the ConfigureFabricProfileCommand is not really well implemented. It modifies the overlord-commons profile and the s-ramp profile as well.
The good solution would be to have an Sramp FabricConfiureCommand (in the s-ramp-karaf-commands) and a FabricConfigureCommand (in the overlord-commons-karaf-commands).
> Improve s-ramp commands for Fuse/Fabric
> ---------------------------------------
>
> Key: SRAMP-570
> URL: https://issues.jboss.org/browse/SRAMP-570
> Project: S-RAMP
> Issue Type: Enhancement
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> For Fuse:
> 1.) Make the password argument optional
> 2.) If no Overlord installation has been attempted (the existence of overlord.properties in FUSE/etc is a good test), fail if no password is provided
> 3.) If a password is provided, but overlord.properties already exists, print what Gary mentioned: an installation already exists, re-using those credentials, but the "overlord:changePassword" command is available
> 4.) Create overlord:changePassword. It would regenerate the keystore and update any applicable *.properties values
> Modify/Add commands to deploy in Fuse Fabric. Create new commands. They would be like fuse commands, but starting by fabric : fabric:overlord:s-ramp:configure
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (SRAMP-570) Improve s-ramp commands for Fuse/Fabric
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-570?page=com.atlassian.jira.plugin.... ]
Brett Meyer edited comment on SRAMP-570 at 9/22/14 10:17 AM:
-------------------------------------------------------------
[~virchete], not sure that we need new Fabric commands at all. The overlay zip, provided by the fsw-fuse project, will continue to be the installation method. Your original ConfigureFabricProfilesCommand should be all that's needed (overlord:configureFabric). I'd vote to simply leave that as-is.
was (Author: brmeyer):
[~virchete], not sure that we need new Fabric commands at all. The overlay zip, provided by the fsw-fuse project, will continue to be the installation method. Your original ConfigureFabricProfilesCommand should be all that's needed. I'd vote to simply leave that as-is.
> Improve s-ramp commands for Fuse/Fabric
> ---------------------------------------
>
> Key: SRAMP-570
> URL: https://issues.jboss.org/browse/SRAMP-570
> Project: S-RAMP
> Issue Type: Enhancement
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> For Fuse:
> 1.) Make the password argument optional
> 2.) If no Overlord installation has been attempted (the existence of overlord.properties in FUSE/etc is a good test), fail if no password is provided
> 3.) If a password is provided, but overlord.properties already exists, print what Gary mentioned: an installation already exists, re-using those credentials, but the "overlord:changePassword" command is available
> 4.) Create overlord:changePassword. It would regenerate the keystore and update any applicable *.properties values
> Modify/Add commands to deploy in Fuse Fabric. Create new commands. They would be like fuse commands, but starting by fabric : fabric:overlord:s-ramp:configure
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months