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
Tracking issue for refactoring s3 to include compile time + runtime time flag
Current implementation - We are building 2 docker images, one image contains all the release features including kms, s3, etc and other without these features which are getting pushed to the public docker hub. This was to ensure that anyone who wants to try out Hyperswitch locally by pulling the pre-built docker image, it shouldn't be a hassle for he/she to setup s3. For this very reason we were pushing 2 docker images which was a temporary solution
Possible Implementation
Providing support for enabling or disabling s3 feature in runtime so that we no longer have to build 2 images.
Feature Description
Tracking issue for refactoring
s3
to include compile time + runtime time flagCurrent implementation - We are building 2 docker images, one image contains all the release features including
kms
,s3
, etc and other without these features which are getting pushed to the public docker hub. This was to ensure that anyone who wants to try out Hyperswitch locally by pulling the pre-built docker image, it shouldn't be a hassle for he/she to setups3
. For this very reason we were pushing 2 docker images which was a temporary solutionPossible Implementation
Providing support for enabling or disabling s3 feature in runtime so that we no longer have to build 2 images.
Tasks
s3
feature flag toaws_s3
#3340s3
to extend other storage logics and provide a runtime flag for the same #3347Have you spent some time checking if this feature request has been raised before?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: