Our Jira DC (9.12.x) is running on OpenShift.
We use the filestore-config.xml to setup our own S3 Bucket.
The feature flag was enabled correctly as per these instructions.
We have start the pod and in the jira-log we can read this:
"logger":"com.atlassian.jira.filestore.FileStoreSwitcher",
"message":"Due to the feature com.atlassian.jira.attachments.storage.configurable being disabled, the attachments storage is not configurable. Defaulting to attachments stored in the Jira home"
But for avatars ist works and they are stored in our S3 Bucket
What we are missing? Or is it not support on Jira?
if i call GET on the "DarkFeature" <baseURL>/rest/internal/1.0/darkFeatures/com.atlassian.jira.attachments.storage.configurable
It returns "{"enabled": true}" so why the FileStoreSwitcher says it it disabled?
We found the "problem" ... it was the way how we enable the "DarkFeature"
On that page How to manage dark features in Jira | Jira | Atlassian Documentation the sentence
In order to enable a feature flag, type <feature_flag_name>.enabled in the Enable dark feature text area and click the Add button.
does not work with that DarkFeature.
We only have to add "com.atlassian.jira.attachments.storage.configurable" without the ".enabled" at the end and now it works as expected.
We can upload Attachment and they will be saved at the S3 Bucket.
Unfortunately, the corresponding rest call now shows "false". <baseURL>/rest/internal/1.0/darkFeatures/com.atlassian.jira.attachments.storage.configurable BUT it works.
@Sven Finsterwalder you need to enable this dark feature. See the warning block in https://confluence.atlassian.com/adminjiraserver0912/storing-attachments-in-amazon-s3-1346048178.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, but as I wrote above "The feature flag was enabled correctly as per these instructions." It is enabled.
And I have also restart the pod, but the flag seems to be ignored.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, I missed it completely that you did enabled this feature. It should be supported for this Jira version as far I know, but I am not a Jira SME.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
no problem.
On that page Configuring file attachments | Administering Jira applications Data Center 9.12 | Atlassian Documentation
there is one sentense:
"This feature isn't supported for on-premise deployments or for any customers not running Jira in AWS."
So did we need a real AWS Bucket?
I wish I could take a look in the FileStoreSwitcher class ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you need to configure 2 separate s3-filestore ids - for avatars and attachments, and pre-create AWS S3 buckets for each of those.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For now I have disabled the entry for avatars and deploy it again, restart the pod and it does not work.
The "FileStoreSwitcher" says again "Due to the feature com.atlassian.jira.attachments.storage.configurable being disabled, the attachments storage is not configurable..."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But you did specify bucket name and region?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yes sure, in my sceenshot above i made it invisible.
if i call GET on the "DarkFeature" <baseURL>/rest/internal/1.0/darkFeatures/com.atlassian.jira.attachments.storage.configurable
It returns "{"enabled": true}" so why the FileStoreSwitcher says it it disabled?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.