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.

Sign up for GitHub

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

Jump to bottom

keep multiple traces #11

Closed
nikaro opened this issue Nov 11, 2021 · 0 comments · Fixed by #12
Closed

keep multiple traces #11

nikaro opened this issue Nov 11, 2021 · 0 comments · Fixed by #12

Comments

@nikaro
Copy link
Contributor

nikaro commented Nov 11, 2021

Currently this plugin keep only one trace.json, thus not allowing to run multiple plays and have the trace for each of them.

I suggest to :

  • change the default output directory to ./trace (or something else) to avoid cluttering the current dir with too many files
  • change the output file to something like play-<timestamp>-<playbook_name>.json
  • add an option to set a rotation for these trace files (ie. keep only 30 of them)

I already have proof of concept locally, if you are OK with i can submit a pull request that we can discuss further.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Keep multiple traces
1 participant
@nikaro