Pandoc - gitlab - authentication token

Pandoc - gitlab - authentication token

[Rajko Albrecht]

[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]

Hi, I searched for days and didn't found a solution.

I generate pdf from a gitlab project wiki. The markdown files are localy 
checked out, so no problem using

pandoc wiki/home.md -t latex -o example.pdf 

But the problem starts when the md has images insight which are rendered by 
gitlab on access (pipline status etc.). Then I just get the error 

[pandoc warning] Could not find image 'https://gitlab.xxxx/coverage.svg', 
skipping ....

I tried various variants giving the authentication information to pandoc, 
.netrc isn't read (and not usefull), gitlab requires a  header 
"PRIVATE-TOKEN: XXXXXXXXX" for download. With curl I can set it and it 
works. Using wrapper script eg pipline does not work 'cause wiki pages are 
stored inside a git.

So - is there any solution giving pandoc authorisation tokens on 
commandline for retrieving remote content? I didn't found something in any 
documentation... 

Bye

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/8994b4ee-2b9c-4b53-b6cd-109bfae40189%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 3092 bytes --]

Re: Pandoc - gitlab - authentication token

[John MacFarlane]

No way to do this currently.

There is code in openURL (in Text.Pandoc.Shared) that sets
the USER_AGENT header if the USER_AGENT environment variable is set.

One could do something similar for PRIVATE-TOKEN, but I
worry about doing this kind of thing on an ad hoc basis.

Perhaps a more principled approach would be to add a
CLI option that could be repeated and that worked like
the current -V option:

    pandoc --request-header USER_AGENT="Blah blah"
      --request-header PRIVATE-TOKEN="XXXXX"

This would give the needed flexibility...

+++ Rajko Albrecht [Oct 14 17 00:59 ]:
>   Hi, I searched for days and didn't found a solution.
>   I generate pdf from a gitlab project wiki. The markdown files are
>   localy checked out, so no problem using
>   pandoc wiki/home.md -t latex -o example.pdf
>   But the problem starts when the md has images insight which are
>   rendered by gitlab on access (pipline status etc.). Then I just get the
>   error
>   [pandoc warning] Could not find image
>   'https://gitlab.xxxx/coverage.svg', skipping ....
>   I tried various variants giving the authentication information to
>   pandoc, .netrc isn't read (and not usefull), gitlab requires a  header
>   "PRIVATE-TOKEN: XXXXXXXXX" for download. With curl I can set it and it
>   works. Using wrapper script eg pipline does not work 'cause wiki pages
>   are stored inside a git.
>   So - is there any solution giving pandoc authorisation tokens on
>   commandline for retrieving remote content? I didn't found something in
>   any documentation...
>   Bye
>
>   --
>   You received this message because you are subscribed to the Google
>   Groups "pandoc-discuss" group.
>   To unsubscribe from this group and stop receiving emails from it, send
>   an email to [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/8994b4ee-2b9c-4b53-
>   b6cd-109bfae40189%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/8994b4ee-2b9c-4b53-b6cd-109bfae40189-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout

Re: Pandoc - gitlab - authentication token

[John MacFarlane]

I've just added this.  (And removed the hacky sensitivity
to the USER_AGENT env variable.)

>Perhaps a more principled approach would be to add a
>CLI option that could be repeated and that worked like
>the current -V option:
>
>   pandoc --request-header USER_AGENT="Blah blah"
>     --request-header PRIVATE-TOKEN="XXXXX"
>
>This would give the needed flexibility...
>
>+++ Rajko Albrecht [Oct 14 17 00:59 ]:
>>  Hi, I searched for days and didn't found a solution.
>>  I generate pdf from a gitlab project wiki. The markdown files are
>>  localy checked out, so no problem using
>>  pandoc wiki/home.md -t latex -o example.pdf
>>  But the problem starts when the md has images insight which are
>>  rendered by gitlab on access (pipline status etc.). Then I just get the
>>  error
>>  [pandoc warning] Could not find image
>>  'https://gitlab.xxxx/coverage.svg', skipping ....
>>  I tried various variants giving the authentication information to
>>  pandoc, .netrc isn't read (and not usefull), gitlab requires a  header
>>  "PRIVATE-TOKEN: XXXXXXXXX" for download. With curl I can set it and it
>>  works. Using wrapper script eg pipline does not work 'cause wiki pages
>>  are stored inside a git.
>>  So - is there any solution giving pandoc authorisation tokens on
>>  commandline for retrieving remote content? I didn't found something in
>>  any documentation...
>>  Bye
>>
>>  --
>>  You received this message because you are subscribed to the Google
>>  Groups "pandoc-discuss" group.
>>  To unsubscribe from this group and stop receiving emails from it, send
>>  an email to [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>  To post to this group, send email to
>>  [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>  To view this discussion on the web visit
>>  [3]https://groups.google.com/d/msgid/pandoc-discuss/8994b4ee-2b9c-4b53-
>>  b6cd-109bfae40189%40googlegroups.com.
>>  For more options, visit [4]https://groups.google.com/d/optout.
>>
>>References
>>
>>  1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>>  2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>>  3. https://groups.google.com/d/msgid/pandoc-discuss/8994b4ee-2b9c-4b53-b6cd-109bfae40189-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>>  4. https://groups.google.com/d/optout
>
>-- 
>You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
>To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20171016032842.GB45185%40Johns-MacBook-Pro.local.
>For more options, visit https://groups.google.com/d/optout.