-
Notifications
You must be signed in to change notification settings - Fork 48
Variables parameter set to no_log=True #170
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
base: main
Are you sure you want to change the base?
Variables parameter set to no_log=True #170
Conversation
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 11m 31s |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #170 +/- ##
==========================================
+ Coverage 73.00% 80.09% +7.08%
==========================================
Files 16 23 +7
Lines 1015 1522 +507
Branches 182 274 +92
==========================================
+ Hits 741 1219 +478
- Misses 243 262 +19
- Partials 31 41 +10
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This requires a changelog, and the linters
workflow should be fixed, but this is not related to this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will need a changelog.
Maybe I'm not fully understanding the issue, but isn't this change going to make it even harder to debug? Setting no_log
at the module level can't be overridden.
Changelog added. @gravesm sometimes debugging doesn't require debugging the modules |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 12s |
SUMMARY
The
variables
parameter often includes sensitive data. Whileno_log=true
can be set on the task level (as suggested in the module's documentation), this hinders efforts to debug module usage during the plan or apply stages of Terraform. It would make more sense just to define thevariables
parameters to be hidden (as some other Ansible modules do).Based on AAPRFE-1929.
ISSUE TYPE
COMPONENT NAME
cloud.terraform.terraform
ADDITIONAL INFORMATION
An even better solution would be to have a new parameter which could switch the
variables
visibility to on/off. I'd need some help with that though.