Closed vkolotov closed 6 years ago
@vkolotov i'm aware of that. What alternatives do you have in mind?
Hi @amtrack,
Two options in mind:
Thanks, Vlad
Hi @vkolotov, that sounds good to me!
Using force-dev-tool in a build script
section in the README. Does that work for you?@amtrack Ah I see now, it was not clear for me. So do I need to set those three variables so that force-dev-tool would pick them up?
BTW, what I did to keep it safe is another option:
#!/bin/bash
force-dev-tool remote add ${SFDC_USERNAME} ${SFDC_USERNAME} ${SFDC_PASSWORD} -u ${SFDC_SERVER_URL} --default
/bin/bash scripts/pull-from-sf-push-to-git.sh
force-dev-tool remote remove ${SFDC_USERNAME}
I'm not planning to implement this as people already have moved or will move to using sfdx
instead.
Passwords for salesforce are kept unencrypted in a plain json file (config/.orgs.json). Easy to steal.