Removing need for bash script

Change-Id: I447ed1d0e791ee38f4434d78a450edc02c222816
Issue-ID: INT-949
Signed-off-by: AndyWalshe <andy.walshe@est.tech>

1 files changed, 25 insertions, 0 deletions

diff --git a/test/mocks/pnf-onboarding/README.md b/test/mocks/pnf-onboarding/README.md
new file mode 100644
index 000000000..8440b3483
--- /dev/null
+++ b/test/mocks/pnf-onboarding/README.md
@@ -0,0 +1,25 @@
+
+PNF Package for Integration Test
+================================
+
+**NOTE: Currently this solution only works on Linux OS and requires openssl to be preinstalled.**
+
+This module builds 2 PNF packages based on the files in `/src/main/resources/csarContent/`
+
+1. unsigned package:	`sample-pnf-1.0.1-SNAPSHOT.csar`
+2. signed package:	`sample-signed-pnf-1.0.1-SNAPSHOT.zip`
+
+The signed package is based on ETSI SOL004 Security Option 2. It contains the csar, cert and cms files.
+
+The packages are generated by running the following command in the same directory as this readme file i.e. pnf-onboarding directory:
+>	`$ mvn clean install`
+
+The packages will be stored in the maven generated `target` directory.
+
+To be able to use the signed package in SDC the `src/main/resources/securityContent/root.cert` file has to be loaded into SDC onboarding backend container.
+
+If SDC is running in containers locally then the following commands could be used to copy the root.cert to the default location in SDC Onboarding Container. It is assumed that the commands are executed from inside pnf-onboarding directory.
+
+>	`$ docker exec -it <sdc-onboard-backend-container-id> mkdir -p /var/lib/jetty/cert`
+
+>	`$ docker cp src/main/resources/securityContent/root.cert <sdc-onboard-backend-container-id>:/var/lib/jetty`