-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
None
-
Policy Dublin 4 2/28-3/14, Policy Dublin 5 3/15-4/04
As an ONAP policy developer, I would like to create RESTful API entry points for Create/Read policy templates in the API engine code so that a CSIT test can be developed and S3P stability/performance tests can be developed to test the API engine. Various types of policy templates (i.e. DCAE uS configuration, XACML/DROOLS/APEX) should be covered by these same entry points so that they are generic APIs for Create/Read all kinds of templates. Main entry point includes REST controller code that directs API requests into appropriate service provider methods via annotations and service provider code that implements the API processing workflow.
Acceptance Criteria:
- Code implementation in policy/api
- Junit tests exist in this repo that test RESTful POST/GET on template archetype artifacts for DCAE uS configuration policy, XACML/DROOLS/APEX policies
- Alignment with logging requirements
- https://wiki.onap.org/display/DW/ONAP+API+Common+Versioning+Strategy+%28CVS%29+Guideline
- Alignment with sonar, checkstyle requirements
- Cucumber tests
- HTTPS configurable support
- AAF/CADI support
- CSIT added for these new apis
- S3P add functionality for these new apis
- Documentation
- blocks
-
POLICY-1442 Policy Lifecycle API RESTful Create/Read Main Entry Point for Concrete Policies
- Closed
-
POLICY-1446 Policy Lifecycle API RESTful Delete Main Entry Point for Policy Types
- Closed
- is blocked by
-
POLICY-1270 Policy Lifecycle API RESTful HealthCheck/Statistics Main Entry Point
- Closed
-
POLICY-1273 Policy Type Application Design Requirements
- Closed
- mentioned in
-
Page Loading...