feat: support sandbox instances of salesforce - #6
Conversation
| @@ -1,60 +0,0 @@ | |||
| import { Connection, OAuth2 } from "jsforce"; | |||
There was a problem hiding this comment.
This was split up into multiple files to make it easier to maintain in the future. Each file in the events directory now represents a single lambda event handler.
adampash
left a comment
There was a problem hiding this comment.
Actually just realized: Can you update the Getting started docs?
Codecov Report
@@ Coverage Diff @@
## master #6 +/- ##
==========================================
- Coverage 50% 49.35% -0.65%
==========================================
Files 11 11
Lines 304 308 +4
Branches 44 46 +2
==========================================
Hits 152 152
- Misses 152 156 +4
Continue to review full report at Codecov.
|
|
is this going to get merged? |
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
Closes #3
Adds sandbox support by adding the ability to pass a
--sandbox(or-s, for short) flag to theglide initcommand. When--sandboxis passed to theinitcommand, a boolean"sandbox": trueproperty is added to the resulting json file. This option instructs the authentication layer of glide to use the correct login url (https://test.salesforce.com).Users of glide will be able to generate an additional json config for their sandbox instance by running the init command with the additional
[path]argument to specify the file name that best suits their projects naming conventions.To serve data from their sandbox instance rather than using the default production
glide.jsonfile, they can simply provide the filename as a positional argument to theservecommand.