You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add support for SQL Server database
* Added storage test for mssql. Fixed some issues found. Test not yet passing.
* Indicate the docker image tag to use for the mssql test container
* remove ON CONFLICT from mssql statements (#3002)
* Enabled additional mssql tests. Fixed a few issues with the mssql support
* Why is the makefile not working?
* Fix spaces vs. tabs
* Removed temporary snapshot of the maven-plugin
Co-authored-by: Matthias Bertschy <matthias.bertschy@gmail.com>
.PHONY: mem-multiarch-images ## Builds and pushes multi-arch images for 'in-memory' storage variant. Variables available for override [MEM_DOCKERFILE, IMAGE_REPO, IMAGE_TAG, DOCKER_BUILD_WORKSPACE]
.PHONY: mssql-multiarch-images ## Builds and pushes multi-arch images for 'mssql' storage variant. Variables available for override [MSSQL_DOCKERFILE, IMAGE_REPO, IMAGE_TAG, DOCKER_BUILD_WORKSPACE]
.PHONY: kafkasql-multiarch-images ## Builds and pushes multi-arch images for kafkasql storage variant. Variables available for override [KAFKASQL_DOCKERFILE, IMAGE_REPO, IMAGE_TAG, DOCKER_BUILD_WORKSPACE]
.PHONY: multiarch-registry-images ## Builds and pushes multi-arch registry images for all variants. Variables available for override [IMAGE_REPO, IMAGE_TAG]
Copy file name to clipboardexpand all lines: README.md
+7-3
Original file line number
Diff line number
Diff line change
@@ -12,10 +12,11 @@ This project supports several build configuration options that affect the produc
12
12
13
13
By default, `mvn clean install` produces an executable JAR with the *dev* Quarkus configuration profile enabled, and *in-memory* persistence implementation.
- SQL Server (community contributed and maintained)
19
20
20
21
If you enable one, a separate set of artifacts is produced with the persistence implementation available.
21
22
@@ -42,6 +43,8 @@ This should result in Quarkus and the in-memory registry starting up, with the u
42
43
e.g. a higher logging level.
43
44
-`-Psql` enables a build of `storage/sql` module and produces `apicurio-registry-storage-sql-<version>-all.zip`. This artifact uses `H2` driver in *dev* mode,
44
45
and `PostgreSQL` driver in *prod* mode.
46
+
-`-Pmssql` enables a build of `storage/mssql` module and produces `apicurio-registry-storage-mssql-<version>-all.zip`. This artifact uses `H2` driver in *dev* mode,
47
+
and `SQL Server` driver in *prod* mode.
45
48
-`-Pkafkasql` enables a build of the `storage/kafkasql` module and produces the `apicurio-registry-storage-kafkasql-<version>-all.zip` artifact.
46
49
-`-Pnative`*(experimental)* builds native executables. See [Building a native executable](https://quarkus.io/guides/maven-tooling#building-a-native-executable).
47
50
-`-Ddocker`*(experimental)* builds docker images. Make sure that you have the docker service enabled and running.
@@ -53,7 +56,7 @@ The following parameters are available for executable files:
53
56
54
57
### SQL
55
58
- In the *dev* mode, the application expects an H2 server running at `jdbc:h2:tcp://localhost:9123/mem:registry`.
56
-
- In the *prod* mode, you have to provide connection configuration for a PostgreSQL server as follows:
59
+
- In the *prod* mode, you have to provide connection configuration for a PostgreSQL (or SQL Server) server as follows:
57
60
58
61
|Option|Command argument|Env. variable|
59
62
|---|---|---|
@@ -97,6 +100,7 @@ Hub. There are several docker images to choose from, one for each storage optio
Copy file name to clipboardexpand all lines: TESTING.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ This is the normal mode used when you execute the testsuite. Because Apicurio Re
33
33
The configuration is provided via maven profiles. You can find all the available maven profiles [here](integration-tests/testsuite/pom.xml)
34
34
When executing the testsuite you normally provide two profiles:
35
35
+ test profile (which determines the tests that will be executed), some options are acceptance , multitenancy ,...
36
-
+ storage variant to test (which determines the storage backend that will be deployed, and therefore tested), the available options are: inmemory , sql , kafkasql .
36
+
+ storage variant to test (which determines the storage backend that will be deployed, and therefore tested), the available options are: inmemory , sql, mssql , kafkasql .
37
37
38
38
You can find multiple examples of how to run the testsuite in this mode in our [Github Actions Workflows](.github/workflows/integration-tests.yaml)
0 commit comments