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
Ignore Dry-Runs (--check) #148
Comments
Hey @rntbrgtt and thanks for the issue ! I think we can do that. It would be a setting for the callback and if it determines that I actually have a similar need that I planned on working on soon and while it isn't exactly what you've asked for, how would you feel if dry-run playbooks could be easily identified or filtered ? I don't know exactly what shape or form this would take yet. We currently know if a playbook ran in "--check" through the CLI arguments: We could use the value of |
Hi dmsimard , Thanks for your help and time working on this. We always run dry runs with --check or -C so if you use that to identify it will work for us. Regards, |
Hey @rntbrgtt, I haven't had time for this yet but I'd like to include something for this in v1.5. |
I'm going to test an approach to use labels to highlight check mode, it's WIP here: https://review.opendev.org/#/c/752259/ |
This new configuration option will label playbooks automatically based on CLI arguments picked up by the callback. For example, when "--check" is used, it would label the playbook with the label "check:True" or "check:True" when it isn't used. Related: #148 Related: #119 Change-Id: Ifd475875bf83a21ab35c9cf0ac0410520b98d804
What component is this about ?
I would like to be able to ignore all Dry-Runs (--check) and not save those executions on ARA database.
What is your ARA installation like ?
ARA 1.4.2
Installed from pip
Virtual Env
Debian GNU/Linux 10 (buster)
Mysql Database
What is the idea ?
The idea is to just have the important playbook executions on ARA database.
The text was updated successfully, but these errors were encountered: