Deprecations for v5

[tombruijn]

We need to deprecate some stuff because it's too hard to maintain for us now.

Some suggestions below. Let us know if you agree/disagree or use any of these.

These features will still be present in older versions of backup, =< v5, but going forward Backup will support less features that are not actively used.

core features

• Sudo option Deprecate certain Backup features #853

Databases

• OpenLDAP Deprecate certain Backup features #853
• Riak Deprecate certain Backup features #853

Storages

• Dropbox, v1 is being deprecated in June 2017. Only keep it if we support v2 before that
• FTP Deprecate certain Backup features #853
• Ninefold, removed in ninefold closed shop #757
• Rackspace CloudFiles Deprecate certain Backup features #853

Syncers

• All of them Deprecate certain Backup features #853

Notifiers

• Campfire Deprecate certain Backup features #853
• Nagios Deprecate certain Backup features #853
• Prowl Deprecate certain Backup features #853
• Twitter Deprecate certain Backup features #853
• Zabbix Deprecate certain Backup features #853

[masterT]

I love the syncer feature, I use Rsync.

[tombruijn]

@masterT thanks for the feedback! We're thinking of removing the syncing feature as it doesn't really provide good backups. It's just a mirror of the state of your backup model at a certain time. If a file is removed it's removed in your backup as well. It doesn't provide any versioning or a snapshot of something longer ago than the timeframe of your backup schedule.

[zaolin]

AWS S3 does versioning for you. That's why the syncer feature works for S3 in combination with a database backup!

[dhampik]

@tombruijn why are you removing sudo option?
That's a security concern. I'm using it and sudo is configured for specific user to allow only /bin/tar command, so basically this user is really limited to what he can do.
Does it mean that I'll need to give a full root permissions to the user under which backup is performed?
Isn't it too much?

😞

[Xosmond]

Why are you removing Twitter notifier? Is there a problem with the API?

[stuartellis]

@Xosmond - Making Backup maintainable is a problem. The intention here was to reduce the burden by deprecating things that we don't use ourselves, and so cannot test.

This ticket has been made obsolete by the change in #879, which switches the project to maintenance only. Having said that, I know that we may have to close some issues as "won't fix" because we do not have the means to easily test fixes.

[tombruijn]

I'm also thinking of undoing the commit adding the deprecation warnings.
It confuses people and I'm planning on actually removing the deprecated things anymore

[stuartellis]

@tombruijn - Sounds good to me. One of first steps I have for #884 is to go through the documentation and mark up the bits as basically "supported" or "not really supported".

[tombruijn]

Deprecations reverted in #886
Will be undone in the next release

[tombruijn]

beta 2 released, upgrade if you still get deprecation messages

[jmuheim]

upgrade if you still get deprecation messages

For those wondering how to do that:

$ gem install backup --pre