These are chat archives for azukiapp/azk

18th
Jun 2015
Slobodan Mišković
@slobo
Jun 18 2015 02:53

hi folks, is it possible to do something like this:

    mounts: {
      '/root/.aws': path("~/.aws"),
    },

And have it resolve ~ to current user's home folder? I tried "$HOME/.aws" as well. This is so that I can share my AWS credentials with the image so that every developer just has to configure them once on their system, so if you have suggestions for that it would be good too

Gullit Miranda
@gullitmiranda
Jun 18 2015 02:55
hi @slobo
Unfortunately azk is not yet able to extend environment variables, but are in backlog. (not yet added the issue also :( )
But there is an alternative: D
you can use env.HOME
Slobodan Mišković
@slobo
Jun 18 2015 02:59
hm, i tried path("#{env.HOME}/.aws"), but gave an error, let me try what you showed - i guess string interpolation happens when env is already out of scope...
ok great, path(env.HOME + '/.aws') works. thanks for the quick help
Gullit Miranda
@gullitmiranda
Jun 18 2015 03:01
:D
Slobodan Mišković
@slobo
Jun 18 2015 03:01
now to figure out why aws-cli now sends wrong credentials :)
Gullit Miranda
@gullitmiranda
Jun 18 2015 03:03
We know it's not ideal, but for now it works. If you want to (and can) open the issue, I would appreciate it: D
what’s?
Slobodan Mišković
@slobo
Jun 18 2015 03:04
i see, i had old version of aws-cli in the container
Gullit Miranda
@gullitmiranda
Jun 18 2015 03:04
updating work?
Slobodan Mišković
@slobo
Jun 18 2015 03:05
fixing the config file to old format worked :)
Gullit Miranda
@gullitmiranda
Jun 18 2015 03:05
:smile: less bad!
Slobodan Mišković
@slobo
Jun 18 2015 03:07
#465 posted, thanks
Gullit Miranda
@gullitmiranda
Jun 18 2015 03:09
you are welcome.
you saw the news of 0.14.0?
Slobodan Mišković
@slobo
Jun 18 2015 03:09
have newsletter open in another tab, waiting for a quiet moment to go over it :smile:
Gullit Miranda
@gullitmiranda
Jun 18 2015 03:11
nice, then it would feedback to know felt performance improvements and also the new CLI became more enjoyable.
:D
Slobodan Mišković
@slobo
Jun 18 2015 05:52
just upgraded, seems a bit faster to start. but it still takes a bit, like a second or more, for any azk command to exit after it's finished the output. Is this node.js shutdown time, or, since i've opted into sending usage statistics, am I waiting for something to be sent out? If so, how do I opt out temporarily to see if that's causing the delay?
Gullit Miranda
@gullitmiranda
Jun 18 2015 12:54
are the last two things we are working to improve this (and many other things) for the next version.
to change the status tracker use azk config track-toggle