You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
Currently, the Backup Function creates a single *.tar.gz compressed archive structured with the files/folders required to restore a Portainer instance.
While it is possible to set a password to protect the archive, it is not possible to disable the creation of the archive itself when using an S3 Service to upload the backup.
Describe the solution you'd like
Enabling versioning would allow us to take full advantage of the S3 backup service, reducing space used and simplifying check/restore operations.
With a single compressed archive, this is currently not possible; although partial solutions exist ( local script to extract the archive / pre-process the archive before upload / etc.), the ideal solution would be to have an option to exclude the creation of an archive and upload single files.
[ note: cryptography would be delegated to the S3 service, in case this is a point of concern ]
Describe alternatives you've considered
Local script to interpolate backup files, before uploading to the service of choice. Impractical, adds a layer of complexity.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Is your feature request related to a problem? Please describe
Currently, the Backup Function creates a single *.tar.gz compressed archive structured with the files/folders required to restore a Portainer instance.
While it is possible to set a password to protect the archive, it is not possible to disable the creation of the archive itself when using an S3 Service to upload the backup.
Describe the solution you'd like
Enabling versioning would allow us to take full advantage of the S3 backup service, reducing space used and simplifying check/restore operations.
With a single compressed archive, this is currently not possible; although partial solutions exist ( local script to extract the archive / pre-process the archive before upload / etc.), the ideal solution would be to have an option to exclude the creation of an archive and upload single files.
[ note: cryptography would be delegated to the S3 service, in case this is a point of concern ]
Describe alternatives you've considered
Local script to interpolate backup files, before uploading to the service of choice. Impractical, adds a layer of complexity.
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions