Reading user input from console

[scru...@gmail.com]

Hello guys,

I really like the elegance and power of the Drake tool.
I wonder if there is a way to expect a user input (passwd, etc.).
In one step.

Thanks in advance.

[Aaron Crow]

Hi, without knowing more about what you're trying to do, I'd suggest that you try to avoid expecting user input. It's often better to treat that as settings. For example, you can have settings files and the location of those files can be specified in your workflow as parameters to your scripts.

A common idiom for passwords (as well as other settings) is to put them in your environment and have your Drake script access them that way. E.g., on a bash shell you can do this...

export PASSWORD="our super secret password"

... and then your Drakefile can do something like this:

out.csv <- in.csv
  ruby myscript.rb --password $PASSWORD

I hope that helps. If not, please let us know more about the details of what you need to accomplish.

--
You received this message because you are subscribed to the Google Groups "drake-workflow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drake-workflow+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/drake-workflow.
For more options, visit https://groups.google.com/d/optout.

[scru...@gmail.com]

Thanks for the reply Aaron. Is this the only way? I believe the password may be exposed. If I use the ps command I could see it, for example.

On Friday, September 8, 2017 at 7:21:28 PM UTC-3, Aaron Crow wrote:
> Hi, without knowing more about what you're trying to do, I'd suggest that you try to avoid expecting user input. It's often better to treat that as settings. For example, you can have settings files and the location of those files can be specified in your workflow as parameters to your scripts.
>
>
> A common idiom for passwords (as well as other settings) is to put them in your environment and have your Drake script access them that way. E.g., on a bash shell you can do this...
>
>
> export PASSWORD="our super secret password"
>
>
> ... and then your Drakefile can do something like this:
>
>
> out.csv <- in.csv
>   ruby myscript.rb --password $PASSWORD
>
>
>
>
> I hope that helps. If not, please let us know more about the details of what you need to accomplish.
>
>
>
>
>
>
> On Thu, Aug 24, 2017 at 10:57 AM, <scru...@gmail.com> wrote:
> Hello guys,
>
>
>
> I really like the elegance and power of the Drake tool.
>
> I wonder if there is a way to expect a user input (passwd, etc.).
>
> In one step.
>
>
>
> Thanks in advance.
>
>
>
> --
>
> You received this message because you are subscribed to the Google Groups "drake-workflow" group.
>

> To unsubscribe from this group and stop receiving emails from it, send an email to drake-workflo...@googlegroups.com.

>
> Visit this group at https://groups.google.com/group/drake-workflow.
>
> For more options, visit https://groups.google.com/d/optout.

Thanks for the reply Aaron. Is this the only way? I believe the password may be exposed. If I use the ps command I could see it, for example.

[Aaron Crow]

Ok, sure. Any script you run under Drake should be able to read CLI input normally. E.g., try this step:

out.txt <-
  echo "Speak your secret!"
  read password
  echo $password > $OUTPUT

To unsubscribe from this group and stop receiving emails from it, send an email to drake-workflow+unsubscribe@googlegroups.com.

[scru...@gmail.com]

Thanks you Aaron. The problem was in a docker login usage.