🐛 Bug: Persistence not backing up to S3 on latest version of Noco

[MoeDawood15]

Please confirm if bug report does NOT exist already ?

• I confirm there is no existing issue for this

Steps to reproduce ?

Deploy as ECS task on FARGATE

Set the following variables
NC_S3_BUCKET_NAME | AWS S3 bucket name for S3 storage plugin. |  
NC_S3_REGION | AWS S3 region for S3 storage plugin. |  
NC_S3_ACCESS_KEY | AWS access key ID for S3 storage plugin. |  
NC_S3_ACCESS_SECRET | AWS access secret for S3 storage plugin.

Deploy a new service

Am I missing something , all my permissions are set correctly as this worked previously for me with

AWS_ACCESS_KEY | AWS access key ID for S3 storage plugin. |  
AWS_ACCESS_SECRET | AWS access secret for S3 storage plugin.

This is now deprecated

Desired Behavior

Folder with persistence should be created on S3

This worked fine on the older version

Project Details

Noco DB used on AWS ECS Fargate

Attachments

No response

[pranavxc]

We changed the environment variable and deprecated the old one but forgot to add backward compatibility. We fixed it here - #8526, will make a bug fix release soon with the change.

To confirm the behaviour you can try our dev release image - nocodb/nocodb-daily:0.207.1-20240522-1802

[MoeDawood15]

Hi

Thank you for the prompt response

I will try the image below and await the fix

[NViviers]

Hey, I'm working on the exact same environment as @MoeDawood15, pulling this image seems to help a little bit, but it causes further issues. Our existing user's account details are showing as incorrect, and using the "forgot password" feature gives me this error:

message: Request failed with status code 400

undefined

[pranavxc]

Hey, I'm working on the exact same environment as @MoeDawood15, pulling this image seems to help a little bit, but it causes further issues. Our existing user's account details are showing as incorrect, and using the "forgot password" feature gives me this error:

message: Request failed with status code 400

undefined

Can you check the docker log and share if you found any error logs?

[NViviers]

Absolutely, I've attached the a CSV for the logs.
log-events-viewer-result.csv

[pranavxc]

@NViviers: Can we connect over our discord channel ? https://discord.gg/5RgZmkW (my user id: pranavxc)