The Drupal 8 module has had a few issues that are a result of its stream wrapper implementation. There is another ticket to implement the rewritten stream wrapper from 7.3.x which tries to rely on the AWS SDK's S3 stream wrapper wherever necessary.
For such a major change to the module, we need to do the following:
The next steps:
- General code review
- Solve this issues:
-- #2856612: S3fsStream always uses the credentials not the profile
-- #2854735: Custom hostname not working in Drupal 8
-- #2811455: Allow ACLs to be overridden
-- #2856566: Getting 0 bytes files when copying from remote
-- #2855626: Aws\S3\Exception\S3Exception: Error executing "GetObject" on s3.amazonaws when image not exists.
-- #2858239: Change twig compiled files storage destination
- Update README.txt (done)
- Test, test and test.
In alpha we will work in:
- #2812749: IAM Credentials usage
- #2828403: s3fs module does not validate that the acess key + secret key has the permissions to put/upload the file into the bucket
- #2854683: Port Automated Tests from D7 to D8.8/D9.1
- Performance Issues.
Comments
Comment #2
jansete commentedHaha I've created 8.x-3.x branch ten minutes ago, now it's time to work in it!
Comment #3
steel-track commentedComment #4
steel-track commented@jansete - Awesome! What is your plan? I captured three items above. Is there anything else that needs to be in a 3.x branch? Also, do you agree we should deprecate the 2.x branch after the release of the 3.x branch?
Comment #5
steel-track commentedComment #6
steel-track commentedComment #7
jansete commentedHi steel-track,
Now the 8.x-2.x branch is marked like not supported, I added in the release notes and the project description that update to new branch, and now it's easier because is the same code base.
This is my plan to road to alpha, I hear suggestions:
Basically, it's working the main features of the module working with the last aws sdk and looking into 7.x-3.x integration. Some of them now it's implemented, we have to review in the new way if we needed.
- Public and private streamwrapper replace.
- S3FS use per field.
- S3FS Assets.
- Form and settings.php configuration.
- Updated README.
- Replace Drupal deprecated methods and functions.
- Coding standards.
- Drush integration.
- Resolve errors/warnings related basic use.
- Clean comments.
- Add actions page.
Then, we could work among the alpha end and beta releases in:
- Performance Issues.
- Full testing.
- Bugs.
Please create all issues that you think we need, It's easy to review more little things that all module change code, if we can.
Now I'm going to review again all issue queue for better work organization :D
Comment #8
jansete commentedComment #9
steel-track commentedComment #10
jansete commentedComment #11
jansete commentedComment #12
jansete commentedComment #13
jansete commentedA lot of changes I've made this weekend, we are very close to the alpha1, maybe in the next weekend.
The next steps:
- General code review
- Solve this issues:
-- #2856612: S3fsStream always uses the credentials not the profile
-- #2854735: Custom hostname not working in Drupal 8
-- #2811455: Allow ACLs to be overridden
-- #2856566: Getting 0 bytes files when copying from remote
-- #2855626: Aws\S3\Exception\S3Exception: Error executing "GetObject" on s3.amazonaws when image not exists.
- Update README.txt
- Test, test and test.
In alpha we introduce tests from Drupal 7 and others like:
- #2812749: IAM Credentials usage
- #2828403: s3fs module does not validate that the acess key + secret key has the permissions to put/upload the file into the bucket
Comment #14
jansete commentedComment #15
jansete commentedComment #16
jansete commentedComment #17
jansete commentedComment #18
jansete commentedComment #19
nesimo commentedgreat work
Comment #20
jansete commentedWe have the first alpha :)
https://www.drupal.org/project/s3fs/releases/8.x-3.0-alpha0