Allow to set and run backups using another user via cron

[deepak7340]

No description provided.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Deepak Tiwari seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[puppet-community-rangefinder]

mysql::backup::mysqlbackup is a class

that may have no external impact to Forge modules.

mysql::backup::mysqldump is a class

that may have no external impact to Forge modules.

mysql::backup::xtrabackup is a class

that may have no external impact to Forge modules.

mysql::params is a class

Breaking changes to this file WILL impact these 2 modules (exact match):

• edestecd-mariadb
• brucem-ezpublish

Breaking changes to this file MAY impact these 1 modules (near match):

• willdurand-bazinga

mysql::server::backup is a class

Breaking changes to this file WILL impact these 4 modules (exact match):

• thbe-bareos
• thbe-bacula
• dmcnicks-sympa
• mightp-librenms

This module is declared in 140 of 580 indexed public Puppetfiles.

---

These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

[david22swan]

Functionality looks good on a first pass but would need some test's to back it up before we can merge it in.

[deepak7340]

Hi @david22swan can you please merge this since we need to deploy this in our server.

[LukasAud]

Hi @deepak7340, as @david22swan previously mentioned, the code looks good but we would need you to create some tests to back it up for the future. Additionally, it would be great if you could create a better description for the PR.

It also looks like there are some conflicts that must be resolved before CI can start running.

If you can address those few blockers, we would be happy to review/merge this.