When this default cluster configuration is setup, user have to override complete first cluster. Eg have to set KAFKA_CLUSTERS_0_ZOOKEEPER to empty string to override default localhost.
* inject VERSION to npm build
* [issues#315] add new component VersionApp. Display application version in UI
* [CHORE] Adds info about app vesrsion
* fix mvn envs
* [CHORE] Cleanup and specs
Co-authored-by: mbovtryuk <mbovtryuk@provectus.com>
Co-authored-by: Oleg Shuralev <workshur@gmail.com>
* Return id, version, schema, and subject after creating a new schema
* Throw 422 error code if incoming new schema is unprocessable entity due to invalid fields
* Return 409/Conflict error code if schema is duplicate. Change endpoint of createNewSchema method
* Fix submitting new subject or new version if the subject already exists
* Include schema type to schema objects. By default it's AVRO
* [ISSUE-200] Update FE to support new version of api
* Add one more schema-registry with version 5.5.0 to docker-compose files and app properties
* Upgrade Confluent service versions in tests up to 5.5.0
* Set schemaType is required and ignore when submitting to Schema Registry if it's NULL
Co-authored-by: Oleg Shuralev <workshur@gmail.com>
* - moved testcontainers lifecycle control back to singleton
- changed kafka connect container wait strategy from logs to http
* refactoring
* reduced startup timeout to 5 minutes
* Rename attribute 'schemaName' to 'subject' for consistency with Schema Registry terms
* Refactor 'GET /schemas' and 'GET .../schemas/{subject}/versions' to get the latest schemas data at once
* Fix getting error code from attributes in our custom GlobalErrorWebExceptionHandler
* Map schema registry port to 8081 in kafka-clusters-only.yaml
* Add endpoint to retrieve subjects from schema registry by cluster name
* Add endpoint to retrieve subject versions from schema registry
* Get subject schema by version from schema-registry
* Add ability to create/delete schema subjects in/from schema-registry service
* Create WebClient bean and refactor its usage
* Refactor schema api contract
* Return 'Bad request' if there is 'Internal Server Error' from Schema Registry
* Add GET/PUT methods to get/update a schema compatibility level globally or only for a scepific schema
* Add SchemaRegistryContainer.java and testcontainers dependencies for integration tests
* Add junit-jupiter5 for testing
* Add GET/DELETE actions for the latest schema version
* Add endpoint to check schema compatibility
* Set up configuration for testing
* Add basic test for SchemaRegistryService
* Fix mapping from dto to web model
* Change createNewSchema action's endpoint
* Update tests in SchemaRegistryServiceTests
* Rename getLatestSchema method and update tests
* Add more test in SchemaRegistryServiceTests
* Include compatibility level info to schema response. Change Flux to Mono
* Update tests
* Pass schema-registry url for secondLocal cluster too
* Remove explicit returns of 404 status code (it'll be processed by global error handler)
* Add global error handler to response with exception details
* Autoconfigure WebTestClient in SchemaRegistryServiceTest
* Updated schemas required props.
* Renamed long to int64 params
Co-authored-by: Sofia Shnaidman <sshnaidman@provectus.com>
Co-authored-by: German Osin <german.osin@gmail.com>
