This really saved me. Thank you!

For others, an example:

- name: Log into private registry and force re-authorization
  become: true
  docker_login:
    registry: "{{ docker_repo_hostname }}"
    username: "{{ docker_repo_user }}"
    password: " {{ lookup('file', 'gcr-user.json') }}"
    reauthorize: yes


On Monday, June 19, 2017 at 11:36:01 AM UTC-4, julien singler wrote:
>
> Hi Dmitry,
>
> Almost a year after you, I've the same problem. I guess you fixed your 
> problem another way, but for anyone that is currently in the same 
> situation, I found a trick to not let the lookup interpret your json .. 
>
> By digging on this forum : 
> https://groups.google.com/forum/#!topic/ansible-devel/2C7pl2_kxlY
> They suggests to put a space between your double quote and the accolades : 
> gcloud_token: " {{lookup('file', gcloud_token_file)}}"
>
> And it's working fine with gcr .. No need for your filters like to_json 
> and quote.
> I hope it will help others :)
> Le vendredi 2 septembre 2016 01:03:18 UTC+2, Dmitry Makovey a écrit :
>>
>> is anyone using docker_login with Google Cloud Registry?
>>
>> I am attempting to do so by defining variable for auth token:
>>
>> gcloud_token_file: gcp_sa_account.json
>> gcloud_token: "{{ lookup('file', gcloud_token_file) }}"
>>
>> and then trying to login:
>>
>> docker_login: username="_json_key" password="{{ gcloud_token | to_json | 
>> quote }}" email="{{ docker_auth_email }}" registry="gcr.io" reauthorize=
>> "yes"
>>
>> it looks like ansible instead of picking up "raw" contents of the file 
>> auto-converts it into structure as soon as it notices JSON so I have to 
>> "un-convert" it with to_json, however as soon as I do that it seems like 
>> escaping/quoting goes out the window and I am unable to get login to work 
>> as expected. Using the same gcp_sa_account.json I can login just find using 
>>
>> docker login -e [email protected] -u _json_key -p "$(cat 
>> gcp_sa_account.json)" https://gcr.io
>>
>> I looked online and couldn't find any samples of people using it. is it 
>> just not meant to be functional with GCR?
>>
>

-- 
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/5184a790-d307-4185-918b-001cddeda04e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to