[jira] [Commented] (FINERACT-955) ContentRepository for Google Cloud Storage

["Michael Vorburger (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FINERACT-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103762#comment-17103762 ] 

Michael Vorburger commented on FINERACT-955:
--------------------------------------------

Seeing https://github.com/apache/fineract/pull/865 (for FINERACT-963) reminds me that this issue should ideally include work to create an integration test for that photo upload functionality, if we don't have one already. In an ideal world, we would like that IT to just use the {{FileSystemContentRepository}}. It should however be possible to easily launch the same REST API IT pointing to a non-localhost base URL (e.g. via a System Property). Then it could also be launched to test this functionality on remote deployments such as on Amazon, or https://www.fineract.dev on Google Cloud, and eventually integrated as a post-deployment step into FINERACT-970!

> ContentRepository for Google Cloud Storage
> ------------------------------------------
>
>                 Key: FINERACT-955
>                 URL: https://issues.apache.org/jira/browse/FINERACT-955
>             Project: Apache Fineract
>          Issue Type: New Feature
>            Reporter: Michael Vorburger
>            Priority: Major
>
> Similarly to S3ContentRepository, a {{ContentRepository}} for Google Cloud Storage (GCS) could be useful, for FINERACT-786, and I would use it on https://www.fineract.dev.
> It may actually even be possible to use the S3 API, but a GCS native implementation is probably smoother and easier to use. One thing in particular I'm hoping for is that it could pick up the required authentication when running on GCloud automatically from some service account environment variables which as far as I know are present there; it would be nice, if possible, if there was no need, or as little as possible, need for additional configuration parameters.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)