export-login is too big for env variable

[Anatoli Babenia]

Trying to encrypt macaron for Travis SNAP_TOKEN fails, because data is too large.

[Chris Patterson (cjp256)]

Can you share the steps you took to generate/set SNAP_TOKEN?

Is the variable encoded as base64? (Does it have plaintext in it, e.g. "login.ubuntu.com", "macaroon"?)

The steps I take are available at https://docs.travis-ci.com/user/deployment/snaps/:

$ snapcraft export-login --snaps my-snap-name --channels edge -

...where the sending the data to stdout via `-` argument is crucial. Then I copy the output base64 encoded string and use it with:

$ travis env set SNAP_TOKEN "<token>"

If that doesn't help, mind sharing the number of characters in your token?

$ echo "<token>" | wc -c

[Anatoli Babenia (abitrolly)]

I use `travis encrypt` to paste encrypted var into `.travis.yml` to avoid implicit magic variables in CI scripts.

https://github.com/yakshaveinc/linux/blob/c3ec48685cc0d6d22a4a85d1c5ffbc2e00e61048/.travis.yml#L13

[Chris Patterson (cjp256)]

So I tried `travis encrypt`, and probably got the same error as you:

`data too large - consider using travis encrypt-file or travis env set`

Unfortunately this looks like a limitation of Travis and how you're using it. I do understand your position and your preference, but I don't know we can offer a better solution other than to follow Travis' guidance and use one of the two options above... judging by the results of my searches, you are not alone in hoping for a more ideal solution :-/

[Anatoli Babenia (abitrolly)]

It may help to understand what is the structure of the information in the macaroon and what attributes to its size. Maybe it is possible to store permissions as a bit array?