Skip to content

v2021.3.1 04/10/2021
Compare
Choose a tag to compare
@carlospzurita carlospzurita released this 04 Oct 12:08
· 68 commits to master since this release
v2021.3.1
f0eda89
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

🐛 Bugfixes

This is an exceptional release of the Validator, which includes the latest version of the TEAM Engine. A hotfix was needed on the TEAM engine test driver due to a change in the OGC response and the validator was not able to proccess the new response. As a consequence, all the ETS releated with the OGC validator were not able to run and process the result page

Several issues arose from this problem, see #565, #553, #548, #538,
This release builds on the latest release (v.2021.3).

  • TEAM Engine reference update to treat the new OGC validator response format

  • TestDriver for TEAM Engine updated on validator.war inside INSPIRE validator

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training materal

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf ghcr.io/inspire-mif/helpdesk-validator/inspire-validator:2021.3.1
#Launches a container with the image, exposing it port 8090 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf
Modifying the Docker image

In the inspire-validator ZIP file, you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]
Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to access their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, the validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/etf-config.properties, and modify the etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually, host machines are connected to a private network that accesses the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=127.0.0.1,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out https://docs.docker.com/network/proxy

For further configuration, please download the file inspire-validator-2021.3.1.zip and follow the instructions in the README.md file inside the .zip file.

Assets 4
Loading