You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
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.
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.
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:
This is useful from CI script.
The text was updated successfully, but these errors were encountered: