Changelog¶

All notable changes to api-log-spring-boot-starter are documented here.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

Unreleased ¶

BUILTIN is now the default schema management strategy. v0.2.0 made schema management opt-in with NONE as the default, but that left users without Flyway/Liquibase staring at a "table doesn't exist" error on first boot. v0.3.0 flips the default to BUILTIN — the starter runs CREATE TABLE IF NOT EXISTS automatically via Spring Boot's DataSourceScriptDatabaseInitializer, so the table just exists.
V1.0__create_api_log.sql now uses IF NOT EXISTS clauses, making it idempotent and safe to re-run on every boot. Flyway is fine with this; the version row in flyway_schema_history is what matters, not whether the SQL did anything.

api.log.schema.management=builtin (default) — starter creates the table on startup
api.log.schema.management=flyway — starter registers a FlywayConfigurationCustomizer (requires Flyway on classpath)
api.log.schema.management=none — starter does not touch the schema; you apply the DDL yourself

You had management=flyway set explicitly: no change needed.
You had management=none set explicitly: no change needed.
You did not set management (relying on the v0.2.0 default NONE and applying the DDL elsewhere): either set management=none explicitly to preserve old behavior, or let BUILTIN take over (it's idempotent, so it won't fight your existing table).

BREAKING: schema management is now opt-in. v0.1.0 force-installed Flyway and auto-ran the bundled migration. v0.2.0 makes the consumer choose:
- api.log.schema.management=none (default) — apply the DDL yourself (Liquibase, manual psql, your own Flyway flow)
- api.log.schema.management=flyway — starter registers a FlywayConfigurationCustomizer that adds its location to your Flyway setup
flyway-core and flyway-database-postgresql are now <optional>true</optional> — consumers who want management=flyway must declare Flyway in their own build.
Migration relocated from classpath:db/migration/V1.0__create_api_log.sql to classpath:db/api-log/V1.0__create_api_log.sql so it no longer collides with the consumer's default Flyway location.

If you were depending on v0.1.0's auto-migration:

Add org.flywaydb:flyway-core (and flyway-database-postgresql runtime) to your dependencies.
Set api.log.schema.management=flyway in your config.

If you'd rather apply the schema yourself (recommended for production):

First public release. Repackaged as a standalone Spring Boot starter.

Restructured as standalone Spring Boot Starter library.
- groupId: com.devs.lab → kr.devslab
- artifactId: api-log-starter → api-log-spring-boot-starter
- Java package: com.devs.lab.test.* → kr.devslab.apilog.*
Removed demo application (ApiLogApplication, compose.yaml, Dockerfile.postgres) — pure library.
Removed app-only dependencies: spring-boot-devtools, spring-boot-docker-compose, spring-boot-starter-actuator.
Removed spring-boot-maven-plugin from build (library, not executable jar).

Flyway migration path: db.migration/ → db/migration/ (the dot version wasn't a standard Flyway location and never auto-applied).

LICENSE (Apache 2.0) + NOTICE.
Full pom.xml metadata (licenses, SCM, developers, organization) required for Maven Central publishing.
Bilingual README (English default + README.ko.md).
This documentation site.

Async, event-driven API call logging via ApplicationEventPublisher.
RestApiClientUtil bundled HTTP client with GET / POST × sync / async × raw / typed.
PostgreSQL JSONB storage for request/response/error bodies.
Spring Retry integration with RETRY_ERROR events.
Auto-configuration via ApiLogAutoConfiguration with @ConditionalOnMissingBean overrides.
31 tests including PostgreSQL integration via Testcontainers.