-
Type:
Improvement
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Core
-
Tags:
Now that the binary managers are fully contributed through extension points, we should deprecate the property-based configuration and just use extension point parameters.
This would allow having several S3 connectors configured differently in the same Nuxeo instance.
The extension point can now be configured through:
<extension target="org.nuxeo.ecm.core.blob.BlobManager" point="configuration"> <blobprovider name="default"> <class>org.nuxeo.ecm.core.storage.sql.S3BinaryManager</class> <property name="awsid">your_AWS_ACCESS_KEY_ID</property> <property name="awssecret">your_AWS_SECRET_ACCESS_KEY</property> <property name="region">us-west-1</property> <property name="bucket">your_s3_bucket_name</property> <property name="bucket.prefix">myprefix/</property> <property name="directdownload">true</property> <property name="directdownload.expire">3600</property> <property name="cachesize">100MB</property> <property name="crypt.keystore.file">/my/keystore.jks</property> <property name="crypt.keystore.password">password</property> <property name="crypt.key.alias">mykey</property> <property name="crypt.key.password">password</property> <property name="connection.max">50</property> <property name="connection.retry">3</property> <property name="connection.timeout">50000</property> <property name="socket.timeout">50000</property> </blobprovider> </extension>
Note that NXP-18688 also adds cachecount and NXP-18717 adds cacheminage.
–
Customers needing to connect to more than one S3 binary managers with different configurations are now able to do so.
