I have Discourse deployed in an EKS cluster and utilise IAM Roles for Service Accounts to allow access to 2 S3 buckets - one for assets and one for backups. The flag s3_use_iam_profile is set to true.
My settings are configured so that the backup is daily and should upload to the S3 backup bucket. However, I am seeing the backup run in the logs but when it finishes and should upload to S3 it just skips that step as if it has not been set.
I found this old post - Discourse does not support service account and IAM role for S3 backup - that using IRSA or an IAM profile doesn’t work. Now, if I run the backup manually via the Admin UI it completes and uploads to S3 so is there something else I need to set to make this happen automatically?
Everything looks fine. The pod logs show the automatic backup completing successfully and ending ok. It looks like the check on whether remote is enabled is returning false incorrectly.
1 - When I run the backup manually in the admin UI it completes successfully and the compressed gzip file is uploaded to S3.
2- It looks like the line of code above has changed since v3.0.1 - the line has gone from return unless @store.remote? to return unless store.remote? - my Ruby is not great but Google tells me an @variable is an instance variable of self so is there another setting I need to make to get this to work with v3.0.1 or should I upgrade to v3.0.2?