)]}'
{"playbooks/roles/bifrost-deploy-nodes-dynamic/tasks/main.yml":[{"author":{"_account_id":6133,"name":"yolanda.robla","email":"yroblamo@redhat.com","username":"yolanda.robla"},"change_message_id":"ea94bb435a84fde191f66f8dd6ea17338f6b5a9c","unresolved":false,"context_lines":[{"line_number":30,"context_line":"# NOTE(TheJulia): The first record returned by os_client_config"},{"line_number":31,"context_line":"# is utilized as the default. A user can still define the parameters"},{"line_number":32,"context_line":"# if so desired."},{"line_number":33,"context_line":"- name: \"Set os_client_config\u0027s auth parameters if not aleady set.\""},{"line_number":34,"context_line":"  set_fact:"},{"line_number":35,"context_line":"    auth: \"{{ openstack.clouds[0].auth }}\""},{"line_number":36,"context_line":"    auth_type: \"{{ openstack.clouds[0].auth_type }}\""}],"source_content_type":"text/x-yaml","patch_set":6,"id":"fa6399be_c52500c3","line":33,"range":{"start_line":33,"start_character":55,"end_line":33,"end_character":61},"updated":"2016-10-11 14:04:25.000000000","message":"typo, already","commit_id":"f97bfcf155de1a9b44170f08a98f671936fd015e"}],"releasenotes/notes/os_client_config-support-b1073062d842febb.yaml":[{"author":{"_account_id":5805,"name":"Chris Krelle","email":"nobodycam@gmail.com","username":"nobodycam"},"change_message_id":"cf0c551d4ed0a3b40c4a6b0def29e520a44704cd","unresolved":false,"context_lines":[{"line_number":19,"context_line":"    directly. Only the first entry returned is utilized."},{"line_number":20,"context_line":"  - Log entries where authentication data is read and"},{"line_number":21,"context_line":"    stored have been masked with the ``no_log`` parameter."},{"line_number":22,"context_line":"    Troubleshooting non-standard authentication"},{"line_number":23,"context_line":"    configurations may require modifying the playbooks."}],"source_content_type":"text/x-yaml","patch_set":7,"id":"9a629dbe_12873913","line":23,"range":{"start_line":22,"start_character":4,"end_line":23,"end_character":55},"updated":"2016-11-14 17:43:35.000000000","message":"would it be worth adding (maybe not in this patch itself) a \"mask\" or \"obscure\" log configuration parameter that could easily change this behavior?","commit_id":"2785d1e05860ee1775842517ed86117abeb1ef9e"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"42b1d9d8dfeada524d0021993dc976c28a89d498","unresolved":false,"context_lines":[{"line_number":19,"context_line":"    directly. Only the first entry returned is utilized."},{"line_number":20,"context_line":"  - Log entries where authentication data is read and"},{"line_number":21,"context_line":"    stored have been masked with the ``no_log`` parameter."},{"line_number":22,"context_line":"    Troubleshooting non-standard authentication"},{"line_number":23,"context_line":"    configurations may require modifying the playbooks."}],"source_content_type":"text/x-yaml","patch_set":7,"id":"7a77a97e_a2b52532","line":23,"range":{"start_line":22,"start_character":4,"end_line":23,"end_character":55},"in_reply_to":"7a77a97e_01643447","updated":"2016-11-16 12:40:39.000000000","message":"So that level doesn\u0027t actually help that much since no usable error data gets returned, I was more-so thinking that a user may want to debug out their input data OR pass data directly in a different way.","commit_id":"2785d1e05860ee1775842517ed86117abeb1ef9e"},{"author":{"_account_id":5805,"name":"Chris Krelle","email":"nobodycam@gmail.com","username":"nobodycam"},"change_message_id":"5ab3b7eb0987e87bbaba216c23a5277800423585","unresolved":false,"context_lines":[{"line_number":19,"context_line":"    directly. Only the first entry returned is utilized."},{"line_number":20,"context_line":"  - Log entries where authentication data is read and"},{"line_number":21,"context_line":"    stored have been masked with the ``no_log`` parameter."},{"line_number":22,"context_line":"    Troubleshooting non-standard authentication"},{"line_number":23,"context_line":"    configurations may require modifying the playbooks."}],"source_content_type":"text/x-yaml","patch_set":7,"id":"7a77a97e_01643447","line":23,"range":{"start_line":22,"start_character":4,"end_line":23,"end_character":55},"in_reply_to":"7a77a97e_1a183684","updated":"2016-11-15 23:14:15.000000000","message":"I was thinking more along the lines of:\nno_log: yes -\u003e no_log: {{ hide_auth_logs| default(\u0027yes\u0027) }}","commit_id":"2785d1e05860ee1775842517ed86117abeb1ef9e"},{"author":{"_account_id":5805,"name":"Chris Krelle","email":"nobodycam@gmail.com","username":"nobodycam"},"change_message_id":"3b51e7cffe5b2431d66289a8b373e3b6e8e5615a","unresolved":false,"context_lines":[{"line_number":19,"context_line":"    directly. Only the first entry returned is utilized."},{"line_number":20,"context_line":"  - Log entries where authentication data is read and"},{"line_number":21,"context_line":"    stored have been masked with the ``no_log`` parameter."},{"line_number":22,"context_line":"    Troubleshooting non-standard authentication"},{"line_number":23,"context_line":"    configurations may require modifying the playbooks."}],"source_content_type":"text/x-yaml","patch_set":7,"id":"7a77a97e_90a6a20e","line":23,"range":{"start_line":22,"start_character":4,"end_line":23,"end_character":55},"in_reply_to":"7a77a97e_a2b52532","updated":"2016-11-16 17:46:22.000000000","message":"Ah Thank you, maybe it would be worth rewording to something like:\n\"Troubleshooting non-standard authentication configurations may require modifying the playbooks so users can debug their input OR pass data directly in a different way.\"\n\nThis could be easily done with a follow up.","commit_id":"2785d1e05860ee1775842517ed86117abeb1ef9e"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"4e5a23092765e529f6dddd11d32d620e5489b89f","unresolved":false,"context_lines":[{"line_number":19,"context_line":"    directly. Only the first entry returned is utilized."},{"line_number":20,"context_line":"  - Log entries where authentication data is read and"},{"line_number":21,"context_line":"    stored have been masked with the ``no_log`` parameter."},{"line_number":22,"context_line":"    Troubleshooting non-standard authentication"},{"line_number":23,"context_line":"    configurations may require modifying the playbooks."}],"source_content_type":"text/x-yaml","patch_set":7,"id":"7a77a97e_1a183684","line":23,"range":{"start_line":22,"start_character":4,"end_line":23,"end_character":55},"in_reply_to":"9a629dbe_12873913","updated":"2016-11-15 14:33:32.000000000","message":"Change the behavior of regarding non-standard auth?  I guess the trouble is there are multiple layers of indirection and we may only handle a name of a cloud in bifrost, and it could be down past shade/keystonauth1/os-client-config where things are being leveraged. :\\","commit_id":"2785d1e05860ee1775842517ed86117abeb1ef9e"}]}