Replies: 5 comments
-
#13727 refers to Google Storage which has the same feature which is enabled depending on the bucket configuration. |
Beta Was this translation helpful? Give feedback.
-
I have opened a documentation issue 1. Footnotes |
Beta Was this translation helpful? Give feedback.
-
Thanks for the progress on this!! Am I correct that it is something that is configurable.. but not something that is part of the GUI? If so, then would it be appropriate to make a feature ticket for GUI support too? Assuming it does not actually require anything but GUI development, that might be simple enough that I might be able to wrangle up a pull request... |
Beta Was this translation helpful? Give feedback.
-
Yes, that's right. You can open a feature ticket for the GUI option, but this currently doesn't have a high priority for now on our side. Contributions through pull requests are always welcome but need some upfront discussions as to where the changes should be added within the code. The option is enabled by default but can be manually disabled with the help of the hidden property. |
Beta Was this translation helpful? Give feedback.
-
I would like to access an S3 bucket that is configured for "requester pays". Here is the AWS Documentation for the feature, which allows for one S3 user to pay for uploading and storing data, but another user to pay for downloading the data.
Not only can I not figure out how to do this with the Mountain Duck configuration option, when I see the history of the feature on this project, I find a very ambiguous ticket history indicating that it "is", "is not" but "maybe is supported". #13727 #9807 #8893
It is totally reasonable to decide that a given feature is not something that a project is going to support. But you have tags called "wontfix" and "lowpriority" for a reason. It helps people like me, who are trying to understand if this is a feature that we can look forward to, know if we need to look elsewhere for a project that is going to support this feature.
It also allows outside developers to see that there is a potential feature that they could contribute to your codebase that either would, or would not be welcome..
But as it is, I cannot easily tell where this feature stands. Is this on the roadmap? Is it welcome? Is it something that will never be worked on? Is there a reason why?
This is the fourth time that your users have requested clarity regarding a feature, please consider responding in a manner that will allow for future users to know where they stand on this, rather than having to create a new issues to request the same information again.
Thanks for the work that you do on this project. I use your tools frequently, and find that they generally work well.
Regards,
-FT
Beta Was this translation helpful? Give feedback.
All reactions