You can set your auth parameters within each task of your playbook. Not as convenient, obviously. If you do that, you should not mix env variables with auth params in the playbook. You could also define two clouds in a clouds.yaml file (see http://docs.openstack.org/developer/os-client-config/), one with v2 and the other with v3 and just name the cloud in each task. Again, don't mix env variables and use of clouds.yaml.
On Tuesday, February 16, 2016 at 3:25:50 AM UTC-5, Scott wrote: > > > Thanks for reply. Tried settings as mentioned and now get is "The request > you have made requires authentication. (HTTP 401) (Request-ID: > req-3b396e91-c949-4956-b724-9b716c1f19df)". I know the user I'm using is > OK because when I run the openstack cli using same credentials it works. I > have just noticed that on some of my openstack CLI commands, I need to set > "--os-identity-api-version 3" and some need "--os-identity-api-version > 2.0". This mismatch of APV Version calls is what I think maybe causing the > issue. Have a call to HP to query if this is correct. But is there a way > within the auth section of the module to specify which API version to use? > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/2b0852da-ed6c-4f05-9693-c90fec0d5571%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
