Skip to content

option to specify a script that runs after backups#413

Merged
apenney merged 1 commit intopuppetlabs:masterfrom
igalic:backup-postscript
Feb 10, 2014
Merged

option to specify a script that runs after backups#413
apenney merged 1 commit intopuppetlabs:masterfrom
igalic:backup-postscript

Conversation

@igalic
Copy link
Contributor

@igalic igalic commented Jan 13, 2014

This script could be used to sync backups to a central server, or just
to create a file to let external scripts know that backups are
(sucessfully) done and can be picked up.

The postscript option (defaults to false) and can be either a string or
an array of strings. These strings will be directly put into the
mysqlbackup.sh and as such can either be shell commands, or externally
managed files.

This script could be used to sync backups to a central server, or just
to create a file to let external scripts know that backups are
(sucessfully) done and can be picked up.

The postscript option (defaults to false) and can be either a string or
an array of strings. These strings will be directly put into the
mysqlbackup.sh and as such can either be shell commands, or externally
managed files.
@igalic
Copy link
Contributor Author

igalic commented Feb 7, 2014

tested this in production. Works out fine.

apenney pushed a commit that referenced this pull request Feb 10, 2014
option to specify a script that runs after backups
@apenney apenney merged commit ac42ba4 into puppetlabs:master Feb 10, 2014
@igalic
Copy link
Contributor Author

igalic commented Feb 11, 2014

\o/

@igalic igalic deleted the backup-postscript branch February 11, 2014 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants