[JBoss JIRA] (RTGOV-422) Make ElasticSearch quickstart an "out of the box" EPN in the content folder
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-422?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-422.
------------------------------
Resolution: Done
Thanks Ivan.
Only thing missing is the removal of the old quickstart. If you have no objections, then I will remove it? Currently it does the same as the datastore epn - so the datastore epn can serve as an example.
If we do want a quickstart for ElasticSearch, then we can provide a more directed example, using other event object types possibly, to illustrate some additional capabilities? But that can wait for later.
> Make ElasticSearch quickstart an "out of the box" EPN in the content folder
> ---------------------------------------------------------------------------
>
> Key: RTGOV-422
> URL: https://issues.jboss.org/browse/RTGOV-422
> Project: RTGov (Run Time Governance)
> Issue Type: Sub-task
> Reporter: Gary Brown
> Assignee: ivan mckinley
> Fix For: 2.0.0.Final
>
>
> As discussed in the forum post (item 4), it would be good to have an out of the box capability to store information in ElasticSearch, as Kibana is now a part of the new RTGov UI.
> Therefore it has been agreed to move the current quickstart into the 'contents' folder, and deploy as part of the standard default installation.
> This does not prevent users from modifying this default EPN to customise what information they actually want to store in ElasticSearch - but provides a reasonable starting point.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated SRAMP-395:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1085429
> S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
> ----------------------------------------------------------------------------------
>
> Key: SRAMP-395
> URL: https://issues.jboss.org/browse/SRAMP-395
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 0.4.0 - Tomcat Support
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0 - API Management
>
>
> There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI:
> {code}
> s-ramp:upload /path/to/file.ext "Invalid Type"
> s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here."
> {code}
> The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up.
> We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer).
> For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RTGOV-426) Remove metrics from service list/details UI pages
by Gary Brown (JIRA)
Gary Brown created RTGOV-426:
--------------------------------
Summary: Remove metrics from service list/details UI pages
Key: RTGOV-426
URL: https://issues.jboss.org/browse/RTGOV-426
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.Final
Since we now have integration with ElasticSearch, and use Kibana for visualisng the metric information, we no longer need to show metric details on the service list and details pages.
Therefore these aspects will be removed from the UI and underpinning data model.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months