Validation in a docker container of the API descriptions + documentation

build/

#!/bin/bash

# Copyright ETSI 2017

# See: https://forge.etsi.org/etsi-forge-copyright-statement.txt

cd "$(dirname "$0")"

run_dir="$(pwd)/src"

store_dir="$(pwd)/build"

mkdir -p "$store_dir"

cd docker

./build-container.sh

./run-container.sh "${run_dir}" "${store_dir}"

exit $?

More information at [NFV Solutions wiki](https://nfvwiki.etsi.org/index.php?title=NFV_Solutions).

## Content structure

All the main OpenAPI files should be put in the `src` directory and organized with the following schema:

   src/deliverable-number/api-name/api-name.yaml

e.g.

   src/SOL003/LifeCycleManagement/lifeCycleManagement.yaml

## Building

The build file `.jenkins.sh` will validate the files, evaluate JSON references and store the generated files in the build directory. In case the build is executed by Jenkins, the merged file will be store in a specific directory to be web-served.

To build locally, once Docker is installed, simple run

   $sudo bash .jenkins.sh

and the results will be stored in a `build/` directory in the project folder.

## How to raise issues

Change requests can be filed at [ETSI Forge Bugzilla](https://forge.etsi.org/bugzilla/enter_bug.cgi?product=NFV).

# Copyright ETSI 2017

# See: https://forge.etsi.org/etsi-forge-copyright-statement.txt

FROM alpine:3.6

RUN apk update

RUN apk add bash

RUN apk add nodejs

RUN apk add nodejs-npm

RUN npm install -g swagger-tools@0.10.3

RUN npm install -g json-refs@3.0.2

ADD validate-in-docker.sh /validate-in-docker.sh

RUN chmod +x /validate-in-docker.sh

CMD ["/validate-in-docker.sh", "/work", "/storage"]

#!/bin/bash

# Copyright ETSI 2017

# See: https://forge.etsi.org/etsi-forge-copyright-statement.txt

docker build -t openapivalidator .

 No newline at end of file