Open moneystack-alex opened 4 months ago
@moneystack-alex thanks you for raising the issue. This was intended behavior as we did not want to save the encryption values which could pose a security risk. We'll take this feature request into consideration and see if there is a better way to solve this
Is there an existing issue for this?
Description
Automated backups are not encrypted before uploading to s3, but they should be encrypted using APPSMITH_ENCRYPTION_PASSWORD APPSMITH_ENCRYPTION_SALT
Steps To Reproduce
docker-compose exec appsmith appsmithctl backup --upload-to-s3
On the other hand, when that same command is scheduled to run with cron as shown here, it is not encrypted before uploading to s3.
The backup should be encrypted using the encryption env values provided in the docker.env file:
APPSMITH_ENCRYPTION_PASSWORD APPSMITH_ENCRYPTION_SALT
Public Sample App
No response
Environment
Production
Severity
Medium (Frustrating UX)
Issue video log
No response
Version
self-hosted, 1.28