Apex Editor using Spring Boot

Changed Apex Editor to use Spring Boot (MVC)
Changed all tests to use JUnit 5
Added more tests for policy upload feature
Updated JS files to reflect JSON encoding change
Added Apex Editor README
Changed rest path to /policy/gui/v1/apex/editor

Issue-ID: POLICY-3896
Signed-off-by: danielhanrahan <daniel.hanrahan@est.tech>
Change-Id: I10f1ee3c40244a822a7032b4b24cb02060698fc3
73 files changed
tree: 065f6be626573df3da5df23b3b2d2533cb9ed819
  1. gui-clamp/
  2. gui-common/
  3. gui-editors/
  4. packages/
  5. releases/
  6. .gitignore
  7. .gitreview
  8. INFO.yaml
  9. LICENSE.txt
  10. pom.xml
  11. README.md
  12. version.properties
README.md

Summary

Copyright 2017-2018 AT&T Intellectual Property. All rights reserved. Copyright (C) 2021 Nordix Foundation. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE Full license text at https://creativecommons.org/licenses/by/4.0/legalcode

This source repository contains the ONAP Policy GUI code.

To build it using Maven 3, run: mvn clean install -P docker

Docker image

Maven produces a single docker image containing the policy GUIs. These are exposed on the same port (2443) using different URLs:

Building

You can use the following command to build the policy-gui docker image:

mvn clean install -P docker

Deployment

Currently, the policy-gui docker image can be deployed without configuration. For the GUI container to start correctly, the CLAMP backend policy-clamp-backend should be started first.

For local testing, if the CLAMP backend is running on localhost port 8443, the policy-gui docker container can be started with:

docker run -p 2443:2443 --add-host policy-clamp-backend:host-gateway onap/policy-gui

Client Credentials

A certificate must be added in the browser and is required to log in properly:

org.onap.clamp.p12 (from clamp master) (Password: "China in the Spring")

See onap/clamp repo README for details.