blob: 97f4700dcc4aa73192da324623e2fe029414b111 [file] [log] [blame]
// Do not edit directly!
// This file was generated by camel-quarkus-maven-plugin:update-extension-doc-page
[id="extensions-minio"]
= Minio
:linkattrs:
:cq-artifact-id: camel-quarkus-minio
:cq-native-supported: true
:cq-status: Stable
:cq-status-deprecation: Stable
:cq-description: Store and retrieve objects from Minio Storage Service using Minio SDK.
:cq-deprecated: false
:cq-jvm-since: 1.5.0
:cq-native-since: 1.6.0
ifeval::[{doc-show-badges} == true]
[.badges]
[.badge-key]##JVM since##[.badge-supported]##1.5.0## [.badge-key]##Native since##[.badge-supported]##1.6.0##
endif::[]
Store and retrieve objects from Minio Storage Service using Minio SDK.
[id="extensions-minio-whats-inside"]
== What's inside
* xref:{cq-camel-components}::minio-component.adoc[Minio component], URI syntax: `minio:bucketName`
Please refer to the above link for usage and configuration details.
[id="extensions-minio-maven-coordinates"]
== Maven coordinates
https://{link-quarkus-code-generator}/?extension-search=camel-quarkus-minio[Create a new project with this extension on {link-quarkus-code-generator}, window="_blank"]
Or add the coordinates to your existing project:
[source,xml]
----
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifactId>camel-quarkus-minio</artifactId>
</dependency>
----
ifeval::[{doc-show-user-guide-link} == true]
Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.
endif::[]
[id="extensions-minio-additional-camel-quarkus-configuration"]
== Additional Camel Quarkus configuration
Depending on Minio configuration, this extension may require SSL encryption on its connections. In such cases, you will need
to add `quarkus.ssl.native=true` to your `application.properties`.
See also https://quarkus.io/guides/native-and-ssl[Quarkus native SSL guide] and xref:user-guide/native-mode.adoc[Native mode]
section of Camel Quarkus user guide.
There are two different configuration approaches:
* Minio client can be defined via quarkus properties leveraging the Quarkiverse Minio (see http://github.com/quarkiverse/quarkiverse-minio#configuration-reference[documentation]).
Camel will autowire client into the Minio component.
This configuration allows definition of only one minio client, therefore it isn't possible to define several different minio endpoints, which run together.
* Provide client/clients for camel registry (e.g. CDI producer/bean) and reference them from endpoint.
[source,properties]
----
minio:foo?minioClient=#minioClient
----