Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Ability to provide properties (user / password) from command line #228

Closed
rlouapre opened this issue Apr 30, 2014 · 3 comments
Closed

Ability to provide properties (user / password) from command line #228

rlouapre opened this issue Apr 30, 2014 · 3 comments
Milestone

Comments

@rlouapre
Copy link
Contributor

This is useful from CI script.

@grtjn
Copy link
Contributor

grtjn commented May 1, 2014

Can you elaborate a bit on the use case?

You can add new environments, like my-local, local2, local-deploy, prod2, and put any relevant settings in xxx.properties in deploy/. You can also leave password blank in properties, and it should ask for it in most cases at runtime.

@rlouapre
Copy link
Contributor Author

rlouapre commented May 1, 2014

I need to execute ml command from a build script on a CI server. It does not make sense for security reason to store credentials in configuration in this scenario.

@dmcassel
Copy link
Collaborator

dmcassel commented May 1, 2014

We've agreed (offline) that command-line properties are to be validated against the properties in the files. A command line property that does not correspond to one in the .properties files would trigger an error. The property does not have to be set with a value. So you could set up:

yoda-age=

And then run

./ml local deploy modules --ml.yoda-age=900

dmcassel added a commit that referenced this issue May 1, 2014
@dmcassel dmcassel closed this as completed May 1, 2014
@rlouapre rlouapre mentioned this issue May 1, 2014
@dmcassel dmcassel added this to the v1.6 milestone May 2, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants