Red Hat Bugzilla – Bug 996943
Policy definitions are not stored in the S-RAMP repository as distinct entities
Last modified: 2015-08-02 19:44:28 EDT
Description of problem:
According to PRD/ERD Requirement ID(s): SOA-GOV-7
Policy definitions and enforcement handlers should be able to be stored in the repository as distinct entities. Tooling should enable the user to locate a policy and “assign” to a service.
S-RAMP will be able to extract switchyard policies as a derived artifact. There will be no support for storing BAM policies other than through code artifacts.
Version-Release number of selected component (if applicable):
EAP6.1 + S-RAMP + DTGov aimed for SOA 6.0.0.ER1
Steps to Reproduce:
1. Deploy switchyard-quickstart-policy-* project to S-RAMP
2. Explore S-RAMP repo content in sramp-ui
* SwitchYard policy definitions (security,transaction) are not explicitly listed as distinct entities in S-RAMP(-ui)
* SwitchYard policy definitions (security,transaction) are explicitly listed as distinct entities in S-RAMP and can be associated with Services deployed in repository
The SwitchYard deriver (responsible for auto-deriving content from the switchyard.xml file) pulls out the policy information as simple custom properties rather than distinct derived artifacts. The reason is that the policy in the switchyard.xml is a simple value of an attribute. I used this information as the basis for this:
The JIRA for the development of the switchyard deriver is:
I believe the relevant pull request for the policy attribute is:
Since the policy is just a value in an attribute, there didn't seem to be a point to making it a separate unique artifact (there is no additional meta-data).
If more needs to be done I'm happy to be advised what it is. :)
This SwitchYard deriver is just exploring implementation.bean tag for the 'requires' attribute but security policies are defined in service tag so security/custom policies are just ignored.
Eric Wittmann <firstname.lastname@example.org> updated the status of jira SRAMP-231 to Coding In Progress
Eric Wittmann <email@example.com> updated the status of jira SRAMP-231 to Resolved
Eric Wittmann <firstname.lastname@example.org> updated the status of jira SRAMP-231 to Closed
Eric Wittmann <email@example.com> made a comment on jira SRAMP-231
Note - I added new derived artifacts with type ComponentService. This new artifact type is for the <service> children from a <component> This is where you can find the 'requires' attribute value.
This patch probably hasn't been included in ER2 build. I've deployed SwitchYard application with custom policy defined and an application with security policy defined and no artifacts with 'requires' attribute were found in S-RAMP repository browser (http://localhost:8080/s-ramp-ui/#artifacts).
Stefan, am I correct in assuming that you don't get any derived artifacts of type ComponentService at all?
Your assumption is correct.
(In reply to Eric Wittmann from comment #8)
> Stefan, am I correct in assuming that you don't get any derived artifacts of
> type ComponentService at all?
Verified in FSW 6.0.0.ER3. Artifacts of type SwitchYardComponentService contains 'requires' attribute with appropriate policy type (security,transaction,custom).