Skip to content

Commit

Permalink
Remove tests and documentation for Quarkus Amazon Services integration
Browse files Browse the repository at this point in the history
  • Loading branch information
jamesnetherton committed Nov 20, 2024
1 parent 392304d commit b84a2a6
Show file tree
Hide file tree
Showing 51 changed files with 15 additions and 2,593 deletions.
11 changes: 11 additions & 0 deletions docs/modules/ROOT/pages/migration-guide/3.17.0.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
= Camel Quarkus 3.17.0 Migration Guide

The following guide outlines how to adapt your code to changes that were made in Camel Quarkus 3.17.0.

== Reduced support when using Quarkus Amazon Services extensions with Camel Quarkus AWS2 extensions

Historically, the Camel Quarkus project tested & verified that using https://docs.quarkiverse.io/quarkus-amazon-services/1.x/index.html[Quarkus Amazon Services] extensions in conjunction with Camel Quarkus AWS2 extensions worked successfully.

From Camel Quarkus 3.17.0, this verification step ceases to exist and the Camel Quarkus AWS2 extension documentation no longer makes reference to Quarkus Amazon Services.

If you want to leverage AWS support on Camel Quarkus, the recommended approach is to use the https://quarkus.io/extensions/?search-regex=camel-quarkus-aws2[camel-quarkus-aws2] extensions without Quarkus Amazon Services.
1 change: 1 addition & 0 deletions docs/modules/ROOT/pages/migration-guide/index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@ We do frequent releases, a release almost every month, and even though we strive

Listed here are guides on how to migrate between major versions and anything of significance to watch for when upgrading from minor versions.

* xref:migration-guide/3.17.0.adoc[Camel Quarkus 3.16.x to Camel Quarkus 3.17.0 migration guide]
* xref:migration-guide/3.15.0.adoc[Camel Quarkus 3.14.x to Camel Quarkus 3.15.0 migration guide]
* xref:migration-guide/3.2.0.adoc[Camel Quarkus 2.x to Camel Quarkus 3.2.0 migration guide]
* xref:migration-guide/2.11.0.adoc[Camel Quarkus 2.10.0 to Camel Quarkus 2.11.0 migration guide]
Expand Down
34 changes: 0 additions & 34 deletions docs/modules/ROOT/pages/reference/extensions/aws2-ddb.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -52,37 +52,3 @@ endif::[]
This extension auto-enables SSL support in native mode. Hence you do not need to add
`quarkus.ssl.native=true` to your `application.properties` yourself. See also
https://quarkus.io/guides/native-and-ssl[Quarkus SSL guide].

[id="extensions-aws2-ddb-additional-camel-quarkus-configuration"]
== Additional Camel Quarkus configuration

[id="extensions-aws2-ddb-optional-integration-with-quarkus-amazon-dynamodb"]
=== Optional integration with Quarkus Amazon DynamoDB

If desired, it is possible to use the Quarkus Amazon DynamoDB extension in conjunction with Camel Quarkus AWS 2 DynamoDB.
Note that this is fully optional and not mandatory at all.
Please follow the https://quarkus.io/guides/amazon-dynamodb#configuring-dynamodb-clients[Quarkus documentation] but beware of the following caveats:

1. The client type `apache` has to be selected by configuring the following property:
+
[source,properties]
----
quarkus.dynamodb.sync-client.type=apache
----

2. The `DynamoDbClient` has to be made "unremovable" in the sense of https://quarkus.io/guides/cdi-reference#remove_unused_beans[Quarkus CDI reference] so that Camel Quarkus is able to look it up at runtime.
You can reach that e.g. by adding a dummy bean injecting `DynamoDbClient`:
+
[source,java]
----
import jakarta.enterprise.context.ApplicationScoped;
import io.quarkus.arc.Unremovable;
import software.amazon.awssdk.services.dynamodb.DynamoDbClient;
@ApplicationScoped
@Unremovable
class UnremovableDynamoDbClient {
@Inject
DynamoDbClient dynamoDbClient;
}
----
34 changes: 0 additions & 34 deletions docs/modules/ROOT/pages/reference/extensions/aws2-s3.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -51,37 +51,3 @@ endif::[]
This extension auto-enables SSL support in native mode. Hence you do not need to add
`quarkus.ssl.native=true` to your `application.properties` yourself. See also
https://quarkus.io/guides/native-and-ssl[Quarkus SSL guide].

[id="extensions-aws2-s3-additional-camel-quarkus-configuration"]
== Additional Camel Quarkus configuration

[id="extensions-aws2-s3-optional-integration-with-quarkus-amazon-s3"]
=== Optional integration with Quarkus Amazon S3

If desired, it is possible to use the Quarkus Amazon S3 extension in conjunction with Camel Quarkus AWS 2 S3 Storage Service.
Note that this is fully optional and not mandatory at all.
Please follow the https://quarkus.io/guides/amazon-s3#configuring-s3-clients[Quarkus documentation] but beware of the following caveats:

1. The client type `apache` has to be selected by configuring the following property:
+
[source,properties]
----
quarkus.s3.sync-client.type=apache
----

2. The `S3Client` has to be made "unremovable" in the sense of https://quarkus.io/guides/cdi-reference#remove_unused_beans[Quarkus CDI reference] so that Camel Quarkus is able to look it up at runtime.
You can reach that e.g. by adding a dummy bean injecting `S3Client`:
+
[source,java]
----
import jakarta.enterprise.context.ApplicationScoped;
import io.quarkus.arc.Unremovable;
import software.amazon.awssdk.services.s3.S3Client;
@ApplicationScoped
@Unremovable
class UnremovableS3Client {
@Inject
S3Client s3Client;
}
----
34 changes: 0 additions & 34 deletions docs/modules/ROOT/pages/reference/extensions/aws2-ses.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -51,37 +51,3 @@ endif::[]
This extension auto-enables SSL support in native mode. Hence you do not need to add
`quarkus.ssl.native=true` to your `application.properties` yourself. See also
https://quarkus.io/guides/native-and-ssl[Quarkus SSL guide].

[id="extensions-aws2-ses-additional-camel-quarkus-configuration"]
== Additional Camel Quarkus configuration

[id="extensions-aws2-ses-optional-integration-with-quarkus-amazon-ses"]
=== Optional integration with Quarkus Amazon SES

If desired, it is possible to use the Quarkus Amazon SES extension in conjunction with Camel Quarkus AWS 2 Simple Email Service (SES).
Note that this is fully optional and not mandatory at all.
Please follow the https://quarkus.io/guides/amazon-ses#configuring-ses-clients[Quarkus documentation] but beware of the following caveats:

1. The client type `apache` has to be selected by configuring the following property:
+
[source,properties]
----
quarkus.ses.sync-client.type=apache
----

2. The `SesClient` has to be made "unremovable" in the sense of https://quarkus.io/guides/cdi-reference#remove_unused_beans[Quarkus CDI reference] so that Camel Quarkus is able to look it up at runtime.
You can reach that e.g. by adding a dummy bean injecting `SesClient`:
+
[source,java]
----
import jakarta.enterprise.context.ApplicationScoped;
import io.quarkus.arc.Unremovable;
import software.amazon.awssdk.services.ses.SesClient;
@ApplicationScoped
@Unremovable
class UnremovableSesClient {
@Inject
SesClient sesClient;
}
----
34 changes: 0 additions & 34 deletions docs/modules/ROOT/pages/reference/extensions/aws2-sns.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -51,37 +51,3 @@ endif::[]
This extension auto-enables SSL support in native mode. Hence you do not need to add
`quarkus.ssl.native=true` to your `application.properties` yourself. See also
https://quarkus.io/guides/native-and-ssl[Quarkus SSL guide].

[id="extensions-aws2-sns-additional-camel-quarkus-configuration"]
== Additional Camel Quarkus configuration

[id="extensions-aws2-sns-optional-integration-with-quarkus-amazon-sns"]
=== Optional integration with Quarkus Amazon SNS

If desired, it is possible to use the Quarkus Amazon SNS extension in conjunction with Camel Quarkus AWS 2 Simple Notification System (SNS).
Note that this is fully optional and not mandatory at all.
Please follow the https://quarkus.io/guides/amazon-sns#configuring-sns-clients[Quarkus documentation] but beware of the following caveats:

1. The client type `apache` has to be selected by configuring the following property:
+
[source,properties]
----
quarkus.sns.sync-client.type=apache
----

2. The `SnsClient` has to be made "unremovable" in the sense of https://quarkus.io/guides/cdi-reference#remove_unused_beans[Quarkus CDI reference] so that Camel Quarkus is able to look it up at runtime.
You can reach that e.g. by adding a dummy bean injecting `SnsClient`:
+
[source,java]
----
import jakarta.enterprise.context.ApplicationScoped;
import io.quarkus.arc.Unremovable;
import software.amazon.awssdk.services.sns.SnsClient;
@ApplicationScoped
@Unremovable
class UnremovableSnsClient {
@Inject
SnsClient snsClient;
}
----
34 changes: 0 additions & 34 deletions docs/modules/ROOT/pages/reference/extensions/aws2-sqs.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -51,37 +51,3 @@ endif::[]
This extension auto-enables SSL support in native mode. Hence you do not need to add
`quarkus.ssl.native=true` to your `application.properties` yourself. See also
https://quarkus.io/guides/native-and-ssl[Quarkus SSL guide].

[id="extensions-aws2-sqs-additional-camel-quarkus-configuration"]
== Additional Camel Quarkus configuration

[id="extensions-aws2-sqs-optional-integration-with-quarkus-amazon-sqs"]
=== Optional integration with Quarkus Amazon SQS

If desired, it is possible to use the Quarkus Amazon SQS extension in conjunction with Camel Quarkus AWS 2 Simple Queue Service (SQS).
Note that this is fully optional and not mandatory at all.
Please follow the https://quarkus.io/guides/amazon-sqs#configuring-sqs-clients[Quarkus documentation] but beware of the following caveats:

1. The client type `apache` has to be selected by configuring the following property:
+
[source,properties]
----
quarkus.sqs.sync-client.type=apache
----

2. The `SqsClient` has to be made "unremovable" in the sense of https://quarkus.io/guides/cdi-reference#remove_unused_beans[Quarkus CDI reference] so that Camel Quarkus is able to look it up at runtime.
You can reach that e.g. by adding a dummy bean injecting `SqsClient`:
+
[source,java]
----
import jakarta.enterprise.context.ApplicationScoped;
import io.quarkus.arc.Unremovable;
import software.amazon.awssdk.services.sqs.SqsClient;
@ApplicationScoped
@Unremovable
class UnremovableSqsClient {
@Inject
SqsClient sqsClient;
}
----
2 changes: 0 additions & 2 deletions extensions/aws2-ddb/runtime/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,6 @@
<camel.quarkus.jvmSince>1.0.0</camel.quarkus.jvmSince>
<camel.quarkus.nativeSince>1.0.0</camel.quarkus.nativeSince>
<quarkus.metadata.keywords>Amazon</quarkus.metadata.keywords>
<cq.quarkus.aws.client.baseName>DynamoDB</cq.quarkus.aws.client.baseName>
<cq.quarkus.aws.client.fqClassName>software.amazon.awssdk.services.dynamodb.DynamoDbClient</cq.quarkus.aws.client.fqClassName>
</properties>

<dependencies>
Expand Down
2 changes: 0 additions & 2 deletions extensions/aws2-s3/runtime/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,6 @@
<camel.quarkus.jvmSince>1.0.0</camel.quarkus.jvmSince>
<camel.quarkus.nativeSince>1.0.0</camel.quarkus.nativeSince>
<quarkus.metadata.keywords>Amazon</quarkus.metadata.keywords>
<cq.quarkus.aws.client.baseName>S3</cq.quarkus.aws.client.baseName>
<cq.quarkus.aws.client.fqClassName>software.amazon.awssdk.services.s3.S3Client</cq.quarkus.aws.client.fqClassName>
</properties>

<dependencies>
Expand Down
2 changes: 0 additions & 2 deletions extensions/aws2-ses/runtime/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,6 @@
<camel.quarkus.jvmSince>1.0.0</camel.quarkus.jvmSince>
<camel.quarkus.nativeSince>1.0.0</camel.quarkus.nativeSince>
<quarkus.metadata.keywords>Amazon</quarkus.metadata.keywords>
<cq.quarkus.aws.client.baseName>SES</cq.quarkus.aws.client.baseName>
<cq.quarkus.aws.client.fqClassName>software.amazon.awssdk.services.ses.SesClient</cq.quarkus.aws.client.fqClassName>
</properties>

<dependencies>
Expand Down
2 changes: 0 additions & 2 deletions extensions/aws2-sns/runtime/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,6 @@
<camel.quarkus.jvmSince>1.0.0</camel.quarkus.jvmSince>
<camel.quarkus.nativeSince>1.0.0</camel.quarkus.nativeSince>
<quarkus.metadata.keywords>Amazon</quarkus.metadata.keywords>
<cq.quarkus.aws.client.baseName>SNS</cq.quarkus.aws.client.baseName>
<cq.quarkus.aws.client.fqClassName>software.amazon.awssdk.services.sns.SnsClient</cq.quarkus.aws.client.fqClassName>
</properties>

<dependencies>
Expand Down
2 changes: 0 additions & 2 deletions extensions/aws2-sqs/runtime/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,6 @@
<camel.quarkus.jvmSince>1.0.0</camel.quarkus.jvmSince>
<camel.quarkus.nativeSince>1.0.0</camel.quarkus.nativeSince>
<quarkus.metadata.keywords>Amazon</quarkus.metadata.keywords>
<cq.quarkus.aws.client.baseName>SQS</cq.quarkus.aws.client.baseName>
<cq.quarkus.aws.client.fqClassName>software.amazon.awssdk.services.sqs.SqsClient</cq.quarkus.aws.client.fqClassName>
</properties>

<dependencies>
Expand Down
48 changes: 0 additions & 48 deletions integration-test-groups/aws2-quarkus-client/README.adoc

This file was deleted.

Loading

0 comments on commit b84a2a6

Please sign in to comment.