search

treasure-data / digdag

Workload Automation System
https://www.digdag.io/
Apache License 2.0
1.3k stars 221 forks source link

Take parameters from a config file in ~/.digdag #53

Closed frsyuki closed 8 years ago

frsyuki commented 8 years ago

Many operators need parameters such as hostname, password, etc. They are connection information. We don't want to put those information in workflow yml file because those files could be uploaded to github.

Idea here is to put those information in a file on home directory. For example, ~/.digdag/config file has following configuration:

client.server-endpoint = ...
client.http-header.authorization = ...
params.td.apikey = ...
params.mysql.hostname = ...
params.mysql.username = ...
params.mysql.password = ...

digdag run and digdag schedule take those parameters.

In this idea, digdag push also takes those parameters and set them to defaultParams of a new revision. This is not always expected behavior especially when a project could be pushed by multiple people. But it's acceptable for now.

frsyuki commented 8 years ago

done by #56.