azionapi-java-sdk

Java client packages for the Azion APIs, generated with OpenAPI Generator (java generator, okhttp-gson library, Java 8 bytecode). Each top-level directory is an independent Maven/Gradle project (org.openapitools:openapi-java-client, package org.openapitools.client) with its own README.md (endpoint and model reference) and docs/.

• JDK 8 or later (CI builds with JDK 17)
• Maven 3 (or the Gradle wrapper shipped in each package)

Every package has the same Maven coordinates, so install the one you need into your local repository and depend on it from your project:

cd personal_tokens
mvn clean install -DskipTests

Authenticate with an Azion personal token in the Authorization header using the Token prefix:

import org.openapitools.client.ApiClient;
import org.openapitools.client.Configuration;
import org.openapitools.client.api.PersonalTokenApi;

ApiClient client = Configuration.getDefaultApiClient();
client.setApiKey(System.getenv("AZION_TOKEN"));
client.setApiKeyPrefix("Token");

PersonalTokenApi api = new PersonalTokenApi(client);
System.out.println(api.listPersonalToken());

Each package README lists every endpoint and model of that API.

Functional tests live in tests/vitest/ and run in CI (.github/workflows/ci-tests.yml):

cd tests/vitest
npm ci
npm test   # needs JDK 17 and Maven on PATH

They compile every package with its own pom.xml, check through a reflection probe (tests/vitest/harness/Probe.java) that every endpoint documented in the package README builds a request with the right HTTP verb and route, and run real HTTP calls against a local API double (authentication header, JSON body, path parameters, model deserialization and ApiException on HTTP errors).

Every push to main is tagged with the next SemVer version (vX.Y.Z) by .github/workflows/bump_version.yml. Notable changes are recorded in CHANGELOG.md.

See CONTRIBUTING.md. Report vulnerabilities privately as described in SECURITY.md.

MIT