-
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 concrete policies 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 concrete policies (i.e. DCAE uS configuration, raw and template-based XACML/DROOLS/APEX) should be covered by these same entry points so that they are generic APIs for Create/Read all kinds of policies. 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 policy artifacts for DCAE uS configuration policy, raw and template-based 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
- Documentation
- blocks
-
POLICY-1447 Policy Lifecycle API RESTful Delete Main Entry Point for Concrete Policies
- Closed
- is blocked by
-
POLICY-1441 Policy Lifecycle API RESTful Create/Read Main Entry Point for Policy Types
- Closed
- mentioned in
-
Page Loading...