Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Add a flag for simulation emails #115

Closed
planetahuevo opened this Issue Sep 4, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@planetahuevo
Copy link

planetahuevo commented Sep 4, 2017

Hi,
When I execute a --simulate I get exactly the same emails as I was doing the proper backup, and this sometimes is scary.
Add a flag to those emails with a [SIMULATE] or [TEST] before the [OK][WARNING] and [ERROR] will help a lot to do testings.

Thanks!

@sebastianfeldmann

This comment has been minimized.

Copy link
Owner

sebastianfeldmann commented Sep 5, 2017

Nice idea

@sebastianfeldmann sebastianfeldmann added this to the 5.1.0 milestone Jan 30, 2018

sebastianfeldmann added a commit that referenced this issue May 4, 2018

Make 'Mail' logger simulation aware - issue #115
In order to decide if mails should be send on simulation
runs each logger now gets passed a system option indicating
if the current run is a simulation.

I added a new option 'sendOnSimulation' (default true) to
the 'Mail' logger to configure its behaviour.
@sebastianfeldmann

This comment has been minimized.

Copy link
Owner

sebastianfeldmann commented May 4, 2018

This will be released with the upcoming version 5.1.0

@planetahuevo

This comment has been minimized.

Copy link
Author

planetahuevo commented May 28, 2018

Hi, I am testing this.
Is there any options to use? Cannot find it on the docs.
Thanks!

@sebastianfeldmann

This comment has been minimized.

Copy link
Owner

sebastianfeldmann commented May 28, 2018

This is currently only available via dev-master, it will be released with version 5.1.0
I hope 5.1.0 will be released in the next 1 to 3 weeks (fingers crossed)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
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.