packages/salesforce: Update docs to reflect the use of optional security token - #11512
Conversation
5668537 to
492cbd5
Compare
25d70ba to
7cf3831
Compare
|
@bacherol This is how README edits are done: Make modifications to: I've also updated the field's description. Also, a changelog entry is required with a version change in root manifest.yml so that updated doc reflects in next patch upgrade. You can take a look at |
🚀 Benchmarks reportTo see the full report comment with |
c5b9fed to
e96f879
Compare
shmsr
left a comment
There was a problem hiding this comment.
I've added the CHANGELOG entry to go with 1.0.0 (GA). So, the changes won't be available until 8.16 stack release. If we 2 more PRs that are scheduled to go in with this 1.0.0 release of Salesforce; so added an entry there itself.
|
💚 Build Succeeded
History
cc @bacherol |
|
@bacherol If the changes looks good; let's merge the PR. |
|
Package salesforce - 1.0.0 containing this change is available at https://epr.elastic.co/package/salesforce/1.0.0/ |
…ity token (elastic#11512) * Update docs --------- Co-authored-by: subham sarkar <subham.sarkar@elastic.co>
…ity token (elastic#11512) * Update docs --------- Co-authored-by: subham sarkar <subham.sarkar@elastic.co>




Proposed commit message
It seems when SF instance demands a security token, it should be added to the password field.
Checklist
changelog.ymlfile.