Validator-Conversion service (VACO) handles its namesake tasks for the common transit standards such as GTFS and NeTEx Nordic profile. The functionality is exposed through a simple Queue API where each VACO task is processed asynchronously and the results are fetched using the Queue API's ticket abstraction.
See Development Environment Setup on Confluence for initial common setup instructions.
- Java 21 LTS+
- Maven 3+
- Docker with Docker Compose
Profile: src/main/resources/application-local.properties
- Create
.envfile at the root of this repository- Ask a fellow team member for a copy of this file and its contents, as it contains secrets which should not be publicly shared
- Start up dev environment with
docker compose up
- Run
VacoApplicationfrom within your IDE of choice or with Mavenmvn spring-boot:run
!! THIS IS NOT A DEVELOPMENT CONTAINER !!
Profile: src/main/resources/application-compose.properties
This variant is meant for testing out alternative environment configurations, container packaging of the application itself and such and is not meant to be and will never be meant to be used as primary way to run the application during development.
- Package the application to container with
mvn clean compile jib:dockerBuild -Djib-maven-plugin.image-name=vaco:latest
- Run the Compose environment with
docker compose --profile containerized up
While mostly everything works as expected, S3 integration has some issues because of S3 local path incompatibility, so it is expected behavior to see
software.amazon.awssdk.core.exception.SdkClientException:
Failed to send the request:
Host name was invalid for dns resolution.
in the logs.
See GitHub Actions workflows in .github/workflows
Swagger documentation is available at path: /api/swagger-ui/index.html
Copyright Fintraffic 2023-2025. Licensed under the EUPL-1.2 or later.